Set up and stop recurring tasks

Configure recurring tasks in Node Cluster, check the next occurrence and use Stop recurrence when you want to end the series.

Use recurrence for a task that repeats, such as a weekly customer follow-up or monthly reporting check. A BAU work-mode label alone does not make tasks recur.

Configure the repeat pattern

1. Open the task’s recurrence control, labeled Set recurrence when no pattern is active.
2. Choose Daily, Weekly, or Monthly under Repeat.
3. Set Every to the interval you need.
4. For Weekly, select weekdays if needed. Leaving them blank uses the weekday of the current due date.
5. Set an optional End date.
6. Choose Save, then check the recurrence indicator and the task’s due date.

Set an intentional due date so the schedule has a clear anchor. The supported next-date calculation uses the previous due date when present. For monthly work, a date beyond the end of the next month is clamped to that month’s final day. Do not assume all subsequent occurrences will return to the original day of the month.

Verify the first repeat

Complete one occurrence through the supported workflow and check the resulting next task, including its date and assignee. The reviewed Canvas recurrence flow creates a next instance when an occurrence is retired and includes limited catch-up handling when the canvas loads.

This is not a promise of an always-running calendar scheduler that creates every missed task while nobody uses the app. If you complete work in another view and the next occurrence is missing, inspect the source Canvas and capture the exact action before creating a replacement manually.

Stop the series deliberately

Open the recurrence control and choose Stop recurrence when the work should no longer repeat. Then review any next occurrence that already exists.

Cancel task is not the same as Stop recurrence. The reviewed recurrence logic treats cancellation as retiring an occurrence and can create the next one. If the intention is to end the series, remove recurrence on the active repeating task before retiring it, and check for already-created instances.

If the next occurrence is wrong or missing

Check the pattern, end date, previous due date, completion state, and whether the next task already exists. Older completed records without a usable completion date can be skipped by catch-up handling. Follow the message shown and establish a clean recurrence configuration on the task you intend to continue.

Ask for support with the task link, source Canvas, pattern, expected date, and action you performed. Avoid bulk recreating missed occurrences until the team understands what the application already generated.