What happens to missed or repeated task runs?

After downtime, Tasks combines missed recurring intervals into one occurrence. It then calculates the next future run. You should not expect a separate catch-up run for every interval that passed.

The occurrence is saved before its due event is published. If publication fails, the pending event can be retried. Delivery is at least once, so an integration can receive the same occurrence more than once.

An integration must recognize the occurrence's stable ID and avoid doing the same work twice. It must also read the current task and occurrence before acting. A schedule change, pause, cancellation, or deletion can make an older due event no longer valid.

Check recorded runs under the task owner's identity:

socra task occurrence list TASK_ID

Replace TASK_ID with the task's ID. Occurrences are listed oldest first. If has_more is true, continue with --after LAST_ID, using the final occurrence ID from each page. Distinct pending occurrences can remain in the history until they are completed or canceled. A pending record alone does not tell you whether an external action already started.

Before manually repeating work, inspect its destination and the Agent's available evidence. Repeating an external action after an uncertain result can create duplicates. Completing an occurrence records completion; it does not undo or repeat the action itself.