Help
Routine skipped
Find why scheduled work did not run and decide whether to request it again.
Skipped means the scheduled work for that record did not execute. A skipped record can cover multiple overdue occurrences. It is not a successful answer, and it may appear only in history rather than as a message in the destination.
Read the reason
- Open Team → Routines.
- Open the Routine's Run history and find the skipped row.
- Read the reason and scheduled time. Check the timezone and destination.
- Use the reason to choose the next action.
| Reason | Next action |
|---|---|
| Earlier Run still active | Inspect that Run before requesting overlapping work. |
| Overdue occurrences | Check the missed period. Decide whether you need one catch-up summary. |
| Local start window expired | Check the selected Local Agent's computer and availability. |
| Routine, Agent, or destination unavailable | Review the saved Routine and restore the required access or destination. |
The history's actual reason takes priority over this list. If it is unclear, keep the Run identifier and message when asking for help.
Request a catch-up deliberately
Do not assume that resume or an instruction edit replays skipped occurrences. If you need the missing work, make a separate request with the exact reporting period and destination. First check earlier Runs and existing results so you do not duplicate published work.
See Routines and Runs or Run status.