When to pause ongoing work
Pause when the objective, source, connected access, schedule, or external conditions need to change. A pause should stop new work while preserving enough state to understand where the routine left off.
- The source of truth is changing or temporarily unavailable
- A connection needs to be refreshed, limited, or replaced
- The result or approval boundary needs to be redesigned
- You no longer need the next scheduled run
Pause cleanly
Before pausing, review what has already completed and whether an action is still waiting for your decision. Pausing should not be treated as undoing work that already happened in an external service.
- Pause the routine before its next run or pending action.
- Review the last completed result and any approval still waiting.
- Confirm whether in-progress work should be preserved or discarded.
- Record the condition that must be true before the routine resumes.
Resume from a confirmed state
Before resuming, confirm the objective and refresh context that may have changed. Dayric should continue from the last reliable state rather than repeat completed actions or assume an interrupted step succeeded.
- Review the cadence, sources, connections, and approval boundary.
- Update any context that changed while the routine was paused.
- Confirm the last external action directly when its status is uncertain.
- Resume and inspect the next result before returning to normal operation.
Change or end a routine
Edit a routine when the recurring objective remains valid but its schedule or method changes. End it when the outcome is no longer needed. Removing a routine stops future runs; it does not remove results already created.