Running a bot on a schedule
Give a graph a calendar so it runs on its own — once at a set time, daily, every other day, weekly, or any combination.
A graph normally runs when you run it. A schedule makes it run on its own: the agent fires it at the times you set, whether or not anyone has the console open, and each run lands in run history like any other. Open a graph and choose Schedule in the right rail, or use Run → Add schedule… from the menu bar.
A bot can carry several rules at once, and its calendar is all of them together. That is how a single bot combines “every weekday at 09:00” with “every other day at 06:30” and a one-off next Tuesday — three rules, one calendar, rather than one contorted expression.
- Once
- Fires at one specific moment, then switches itself off.
- Daily
- Every day, at each time of day you add.
- Every N days
- A true cadence counted from the start date — set N to 2 for every other day. This is not the same as a cron expression, which restarts its count each month.
- Weekly
- The weekdays you pick, optionally every second or third week.
- Monthly
- The days of the month you pick. A rule set to the 31st simply does not run in February; use the last-day option for month end.
- Cron
- An escape hatch for patterns the options above cannot express. Prefer the others where they fit.
Times are wall-clock in the rule’s timezone, which defaults to yours. “Daily at 09:00” stays 09:00 across daylight saving. On the day clocks spring forward, a rule set inside the skipped hour runs as soon as the clock allows rather than being missed; on the day they fall back, a rule inside the repeated hour runs once, not twice.
The calendar in the panel shows every run the rules produce, computed by the same code that fires them — so what you preview is what will happen. Click a day to add a one-off on it. “Next runs” underneath is the quickest way to confirm a rule means what you intended, without waiting a day to find out.
- Run now
- Runs the rule immediately with its preset, and leaves the schedule alone — it never consumes or delays the next real run.
- Preset
- A rule can carry a run preset, so a scheduled run uses the arguments you chose for that schedule rather than empty input.
- If a run is still going
- By default the next occurrence is skipped rather than starting a second run alongside the first.
- If the agent was down
- Recurring rules resume at the next future run rather than firing everything they missed. A one-off still runs, once, when the agent comes back.
A bot with a live schedule is marked Scheduled wherever it is listed, so a graph that runs unattended is never a surprise. The Calendar page collects every scheduled run across all your bots in one place.
Related
- Run a graphRunning & debuggingSupply the input, clear validation, start the run, and find it afterwards.
- Run configuration and presetsRunning & debuggingPer-node arguments for a run, saved as named presets you can duplicate, export, and seed from the last run.
- Read run history and tracesRunning & debuggingThe runs list, per-run traces and logs, and the run pages hanging off a graph.
More in Running & debugging · Search all help