Guide

Schedules

A schedule runs a workflow on a timetable. Add one in the workflow editor under Schedules; changes take effect when you save the workflow.

When it runs

Every hour or every few hours: every 1, 2, 3, 4, 6, 8 or 12 hours, at a minute you choose.
Every day at a time.
On certain days of the week, with Weekdays and Weekends shortcuts.
Once a month, on day 1 to 28 or the last day of the month.
Custom (cron expression): five fields, minute to day of week.

Every schedule has a time zone. The summary under it reads the schedule back in words and lists the next three run times, so you can check it before saving. A new schedule starts as every day at 9:00 in your time zone. A workflow can have up to 20 schedules.

Inputs and profile

If the instructions use $variables, each schedule has its own values for them, so one workflow can run for several cities or accounts. A schedule can't be turned on until every input is filled, so a new one on such a workflow starts paused. A schedule uses the workflow's browser profile unless you choose another one for it.

Missed and overlapping runs

If a schedule's previous run is still queued, running or waiting for you, its next time is skipped rather than stacked. Runs you start yourself, and other schedules, don't block it.
Times missed while the service was unavailable aren't made up later; the schedule continues at its next time.

Emails after scheduled runs

After each scheduled run you get an email at your sign-in address with how it ended, its summary and its result. Runs you start yourself aren't emailed. To get the data too, set Email the store on the schedule (choose Edit on it) to New rows only (rows that run added or changed) or Full store, sent as an .xlsx file. Each schedule has its own setting, so a daily schedule can send new rows while a weekly one sends the full store.

Every run is charged to your balance as it happens; see Balance and billing.