Schedules: a flow that runs itself

The digest that lands before your Monday meeting, the overnight cleanup of yesterday's uploads: a saved flow can run on its own timetable with nobody watching.

Which is exactly why the money rules below exist. A scheduled run spends real money unattended. Arm a schedule you would be happy to pay for every single time it fires, and pause it when you do not need it.

Setting one up

Open the flow in the Builder and press Schedule, or click the clock icon on its card on Workflows. Choose:

• Every hour, Every day (pick the hour) or Every week (pick the day and hour).
• Whether to skip if the previous run is still going (on by default).

Times use the timezone on your profile (Settings → Profile) and stay put across daylight saving. The dialog shows Next run so you can see exactly when it will first fire.

The five rules worth knowing before you arm one

1. Saving never runs it now. A schedule is always armed for its next slot. Changing the time, or un-pausing, re-arms the same way. Configuration can never spend.
2. A missed slot is skipped, not caught up. If FlowArray is down when a slot passes, it does not fire a burst of runs to make up for it — it waits for the next one. Skipping is cheaper than double-spending.
3. Overlaps are skipped by default. If the previous scheduled run is still going when the next slot arrives, that slot is skipped. Untick the option if you genuinely want them to overlap.
4. Rows come from a snapshot. Scheduling from the Builder captures the items grid at that moment (up to 100 rows). Change the grid later and press ↻ on the schedule to re-capture. Flows that fetch their own data — an analytics digest, a report — need no rows at all, so scheduling them from the Workflows page is fine.
5. A paused schedule spends nothing. Pause, resume and delete are all in the same dialog.

There is deliberately no "Run now" button

A test button that spends real money is exactly the surprise charge the arming rule removes. To test, press Run in the Builder, where you can see the cost and the items in front of you.

Afterwards

Runs started by a schedule are badged Scheduled in Runs, and the schedule links to its last run so you can check what it produced. Turn on notifications so an unattended failure reaches you instead of waiting to be noticed.

Related

• Set a daily spend limit before arming anything. Ceilings are counted from booked cost across everyone, every schedule and every trigger.
• If the timing should come from another system rather than the clock, use a trigger instead.
• Schedules are managed by whoever created them, and by admins.