A standing order is created from a single sentence and runs on a schedule, at a fixed time, immediately, or triggered by one of eight recognised events — with its own card in the jobs list showing whether it is running, waiting or stuck.
Contents
Docs overviewFiles · Standing orders, schedule & states
One sentence becomes a card
The “Jobs” window shows everything that runs permanently. Every standing order has one of three kinds — recurring, bound to an event, or a one-off order — and one of four triggers.
The four triggers
-
Schedule
Daily, on weekdays, weekly, monthly, at month-end or hourly, at a fixed time or minute.
-
Fixed time
A single, fixed appointment in time.
-
Immediately
Runs as soon as it is created.
-
Event
Only eight recognised event kinds actually fire: new email, email from someone, invoice recognised, approaching appointment, no reply, file in folder, message on a social channel, a failed order.
The eight states
Scheduled, waiting for a trigger, waiting for approval, running, stuck, done, paused, cancelled. The list’s header line sums them up: “n running · n waiting · n stuck”.
Pausing, deleting, failing
- Pause
- A button in the list — the order stays in place but stops running.
- Delete
- Asks for confirmation first, and also removes the scheduler’s related tracking entries.
- Failure
- The order switches to “stuck” and shows an inline hint — a pause or cancellation you made stays in effect.
A recurring order gets its own conversation on its first run — “view results” jumps there. A run always belongs to that conversation, never to the jobs window itself, and at most one run happens at a time per conversation.
Known gaps in this documentation build (as of 26 Sept 2026)
- In the jobs window, switching tabs, deleting an order and jumping to the conversation thread are without their own automated test; pause/resume is only tested at the core logic level, not through the interface.
How it works — the three autonomy levels in detail Back to filing, versions & deletion