Help/When things break/Work did not run while I was away

Work did not run while I was away

Local scheduled work needs the Mac app running. A near-miss runs on wake; a longer miss is skipped with a note.

A routine that did not fire is nearly always a machine that was asleep rather than a schedule that was wrong.

Agent · Scheduled work
Anything an agent commits to for later becomes a schedule you can see, pause, or cancel. Nothing runs that you cannot find here.

A local agent's scheduled work runs through the Mac app, so it needs the app open and the machine awake. If yours was asleep when something was due, it runs on wake only when that's within 15 minutes; any later and that run is skipped, with a note saying so, and the routine runs at its next scheduled time. A backlog is never replayed. Cloud agents' schedules run on Dock's machines and are unaffected.

Check the schedule itself

Every routine appears in that agent’s Schedule, with its timing and whether it is switched on. A paused routine looks identical to a missed one from the outside, so check that first.

NoteThis is a local-agent problem. An agent running in the cloud does not depend on your Mac being awake, so its routines fire on schedule either way.
Still stuck? Ask your Chief of Staff, or email us.