Manage and troubleshoot recurring Issues

Use the Team directory and Logs to understand what runs next, who can manage it, and why an occurrence needs attention.

Open the Team directory Admin Editor Viewer

Open Team settings → Recurring issues for an accessible Team. The directory shows active schedules only, including the title, timing, next due date, latest generated Issue, and display-safe needs-attention state.

Search is local to the open directory and is not saved as a Team view. Open a card to use the stable schedule editor route.

Stopped schedules remain historical and do not appear in the active directory. Their generated Issues and Log evidence remain available through the normal access rules.

Understand permissions Admin Editor Viewer

Reading a Team or a directly shared Issue does not automatically grant schedule access.

• Team members with the projected Issue create/work capability can create or manage recurrence.
• Workspace governance access can expose Team settings without granting Team Issue work.
• Private-Team non-members cannot enumerate schedule titles, counts, definitions, next dates, failures, or routes.
• Direct-share-only Issue readers can see the shared Issue and display-safe recurring creation context, but not the schedule directory or management actions.
• Archived Teams automatically stop active schedules.

The server rechecks the named capability for every create, edit, duplicate, bulk, stop, and read command. Hidden controls are a convenience, not the security boundary.

Understand when generation runs Admin Editor Viewer

The scheduler evaluates each active Team in its configured timezone, with UTC as the safe fallback. A future occurrence becomes eligible only after its Team-local scheduled due date has passed.

Generation is bounded and concurrency-safe. The schedule and due date uniquely identify an occurrence, and the generated Issue uses a deterministic request key. Delayed or repeated workers therefore create at most one Issue for the slot.

Recover a failed occurrence Admin Editor

1. Open the schedule marked Needs attention.
2. Review the friendly failure classification and Team Logs.
3. Correct the unavailable property, timing, permission, or configuration problem.
4. Save the schedule when a definition change is needed.
5. Allow the scheduler to retry the same occurrence.

Integrity does not advance past a failed occurrence. A successful retry marks the same occurrence recovered, creates the missing Issue once, advances the next due date, and writes readable recovery evidence.

Read Activity, notifications, and Logs Admin Editor Viewer

• The generated Issue's Activity shows that it came from a recurring schedule and names the scheduled due date.
• Eligible assignee/subscriber Inbox and email rows reuse ordinary Issue rules and display-safe snapshots.
• Team and Workspace Logs record schedule creation, edits, stops, first failures, and recoveries with event-time schedule details.
• Repeated failed worker attempts do not create duplicate visible failure events.

Current access is always rechecked before a route or notification opens. Historical snapshots remain readable only through the surface's existing Team/Issue permissions.

Related