Scheduling
Schedules automate recurring or one-off work for agents, chats, and structured sessions. SwarmClaw treats scheduling as an operations surface rather than a basic cron list.
Schedule Console
The Schedules page has three management scopes:
- Live: active, paused, completed, and due schedules
- Archived: schedules removed from live execution but retained for audit and restore
- Runs: recent schedule-origin task history
You can filter by:
- status
- cadence or type
- agent
- search text
Schedule Types
| Type | Behavior |
|---|---|
| cron | recurring cron expression |
| interval | recurring interval |
| once | one-shot schedule that completes after firing |
Schedules can launch:
- a normal task or wake event
- a bounded Structured Session from a saved template/context
Schedule Preflight
Before saving, the schedule sheet validates the draft and shows the next calculated runs from the server.
- cron schedules can set an explicit timezone such as
UTCorAmerica/New_York - cron drafts without a timezone warn that host local time will be used
- recurring schedules can add a stagger window to reduce simultaneous wakeups
- run-once schedules can set a delay and preview the exact queued time
The same preflight is available from automation:
swarmclaw schedules preview --data '{"agentId":"<agentId>","taskPrompt":"Daily report","scheduleType":"cron","cron":"0 9 * * *","timezone":"UTC"}'
Statuses
| Status | Meaning |
|---|---|
| Active | Eligible to run |
| Paused | Disabled temporarily |
| Completed | One-shot schedule already fired |
| Failed | Last execution failed |
| Archived | Removed from live execution but retained for history |
How Routing Works
SwarmClaw stores schedule routing explicitly.
- task schedules enqueue work for the intended agent and linked context
- wake-only schedules can wake a specific chat or session directly
- structured-session schedules launch into the explicit linked context instead of guessing from recent activity
This prevents connector conversations from leaking across senders and keeps schedule follow-ups attached to the right owner thread.
Archive, Restore, and Purge
Normal delete is now Archive.
Archiving a schedule:
- stops future runs
- cancels linked queued or running schedule tasks when possible
- aborts active schedule-run sessions when possible
- preserves run history and audit visibility
Archived schedules can later be:
- restored
- purged permanently
Schedule-Origin Task Cancellation
Schedule-linked tasks support a distinct cancelled outcome.
That means:
- cancelled schedule work does not keep retrying
- aborted in-flight work is not mislabeled as failed
- late follow-up chatter is suppressed after cancellation unless delivery already happened
Human Loop Interaction
Normal chat replies can resolve durable human-loop waits instead of leaving stale mailbox or watch jobs behind. This matters for scheduled and background flows that pause for human input.