Articles in this section

Schedule a flow

A schedule runs a flow automatically at the cadence you choose — every 15 minutes, once a day at 6:05 AM, the first of every month, or any pattern a cron expression can describe. You set it from the integration's Flows tab or from Flow builder, and it takes effect as soon as the flow is on. This article covers the schedule presets and the cron builder, how time zones and daylight saving time affect runs, how integrator.io assigns start minutes, and how to give one source its own schedule.

Run the flow once on demand before you schedule it, to confirm it works; see Run a flow.

Set a schedule

  1. Go to Home home-icon.png, open the integration, and then select Flows.
  2. In the flow's row, select Schedule — Add schedule when the flow has none yet, Edit schedule once it does.
  3. Choose Presets or Use cron expression, set the schedule, and then select Save.

A blue dot on Schedule — in the Flows list and at the top right of Flow builder — shows that the flow has a schedule.

Presets

Frequency offers Once weekly, Once daily, Twice daily (every 12 hours), Every eight hours, Every six hours, Every four hours, Every two hours, Every hour, Every 30 minutes, and Every 15 minutes. Twice daily keeps 12 hours between runs; for two runs closer together, use a cron expression.

Cron builder

When you select Use cron expression, the schedule starts as every 5 minutes; change it before you save. Each part of the expression has its own control:

Part Options
Minute Every n minutes — a slider from 5 to 55. Each selected minute — 5, 20, 35, or 50, the start minutes integrator.io assigns within an hour.
Hour Every hour; Every n hours (1 to 23); or Each selected hour — any of 00 to 23.
Day of month Every day, or Each day — any of 01 to 31.
Month Every month, or Each selected month.
Day of week Every week, or Each week — any days of the week.

Reset clears the expression. To write an expression by hand, see Cron expression syntax.

Time zone and daylight saving time

A schedule runs in the Time zone you set on it. If you don't set one, it uses the account owner's profile time zone, and if that isn't set, UTC.

The scheduler doesn't adjust for daylight saving time. A flow scheduled for 1:30 AM on the night clocks go back runs twice; one scheduled for 2:30 AM on the night clocks go forward is skipped until the next day.

How start minutes are assigned

integrator.io spreads scheduled starts across the platform so every flow starts promptly: you choose the cadence, and integrator.io assigns the exact start minute. A schedule set for :00, :15, :30, or :45 is saved as :05, :20, :35, or :50 — a daily 5:00 AM schedule runs at 5:05 AM — whether you set it in the schedule editor or through the API. The assigned minute can change, so treat the schedule shown after you save as the start time.

If a process must start at an exact minute, choose the nearest assigned time, or start the run from your own scheduler through the integrator.io API; the run is queued and starts as soon as capacity allows, and the request is rejected if a run of the flow is already queued. See Trigger a flow run in the API reference.

When a run is still in progress

A scheduled start that comes due while the previous run of the same flow is still queued or running is skipped, not queued; the schedule resumes at the next start after that run ends. This applies to every schedule type. So:

  • A run that hangs — for example, behind a backed-up destination — looks like skipped runs for as long as it hangs. Cancel it and run the flow on demand to catch up, then find out why it hung. See Cancel a flow run.
  • A flow whose runs take longer than its interval runs less often than scheduled. If every start matters, lengthen the interval or shorten the run.

Override the flow schedule for one source

When a flow has more than one source, each source normally runs on the flow's schedule, one after another. To run one source on its own cadence, give it a schedule override. An override applies only to that source; sources without one keep the flow schedule, and if every source has an override, the flow schedule is ignored.

  1. Go to Build build-icon.png > Flows, and then open the flow.
  2. Point to the source step, select Actions elipses-button.png, and then select Schedule override.
  3. Set the schedule as you would for the flow, and then select Save.

Run a flow at several specific times a day

A cron expression pairs one set of minutes with one set of hours, so a single schedule can't run a flow at 9:10 AM, 12:30 PM, and 4:00 PM. Choose one of these instead:

  • Use the same minute in each hour. ? 10 9,12,16 ? * * runs at 9:10 AM, 12:10 PM, and 4:10 PM.
  • Give each start time its own source. Add a copy of the export to the flow for each time, and give each source a daily schedule override. All the sources feed the same downstream steps. Each copy of a delta export keeps its own last-run time, so the copies export overlapping records; that's fine when the import updates matching records rather than creating them, or when the export isn't a delta export. Otherwise the flow can import a record more than once.
  • Clone the flow and give each clone its own schedule; see Clone a flow.
  • Start the run from an external scheduler through the API, as described above.

Start-minute assignment still applies: 12:30 PM runs at 12:35 PM, while 9:10 AM runs at 9:10 AM.