| Today’s trigger time has already passed | The schedule may move to the next valid occurrence rather than create a retroactive task. | Set a later trigger time if the task must still generate today, or manually create today’s task and let recurrence begin next cycle. |
| Holiday announced before the trigger | If the holiday is not in the Company Holiday Calendar, the recurrence cannot treat it as a holiday. | Update the HR holiday calendar before the trigger and check the next-run preview. |
| Holiday announced after the task was generated | A calendar update may not retroactively change an already-created task. | Manually reschedule/adjust the generated task and document the reason. Do not assume automatic retroactive correction. |
| Public holiday calendar is empty | Only configured weekly-off information is available. | Add approved holidays in HR settings; recheck recurring schedules that depend on holiday logic. |
| Trigger lands on a weekly off/holiday | The occurrence may run, skip or move depending on the selected rule. | Choose the rule intentionally and verify the next run. |
| Due date lands on a holiday but trigger date does not | The UI wording specifically describes non-working-day handling for an “occurrence”; it does not explicitly show separate due-date adjustment. | Choose due offsets carefully and test/verify the resulting generated task. Adjust deadlines manually if your policy requires working-day due dates. |
| Moved occurrence collides with another scheduled occurrence | Moving to the next working day can bring two occurrences close together. | Check upcoming dates when holidays cluster. If duplicate work would be meaningless, pause/edit the series or skip the affected occurrence operationally. |
| Monthly date is 29/30/31 | Shorter months can break a fixed day-of-month pattern. | Use Last day of month where available and verify February/30-day months in Schedule Status. |
| Annual schedule uses 29 February | Non-leap years require special handling. | Test the yearly behavior. If the intent is “last day of February,” use a last-day rule where supported or manage the exception explicitly. |
| Timezone is changed | Generation time can shift for users/regions. | Use the business timezone that should control the process and recheck preview after any timezone change. |
| Assignee leaves or changes project | Future target mapping may no longer be valid. | Review recurring definitions during offboarding/internal transfers and edit or pause affected definitions. |
| Project is archived/closed | Future recurring work may continue targeting a project that is no longer active, depending on system rules. | Pause or archive the recurring definition as part of project closure. |
| Definition is edited close to trigger time | A run may already be queued or generated. | Avoid last-minute edits where possible; after editing, check the task list and next-run status for duplicate/missed work. |
| Definition is paused with open generated tasks | Pausing future generation does not imply existing open tasks are completed. | Review and close/reschedule already-generated tasks separately. |
| Approval/escalation rule is missing or changed | Generated tasks may not follow the intended governance. | Verify Approval Line and Escalation Path before creation and after workflow-policy changes. |
| Reporter intentionally left blank | Ownership/reporting can be misunderstood. | Use the UI note: blank means each selected person is their own reporter; set one only when the same reporter should apply to all generated tasks. |
| End Date is before the next valid run | No future task may be generated. | Compare the end condition with Schedule Status before creating/saving. |
| Targeting is changed after setup | The future fan-out can differ from the original count. | Recheck the bottom task/person/project summary after any targeting edit. |
| Same person is selected in multiple project contexts | The definition can fan out into multiple task instances. | Confirm the intended person–project pairings and the Review count before Create. |
Actions on an existing Global Recurring Task.