Recurring schedule
A cron expression that fires again and again
Scheduled executions
Single runs booked for one future time
Add a recurring schedule
Open the Recurring Schedule view and select Create Schedule. A workflow can hold several schedules at once.
Save the schedule and it appears as a card. The card carries a switch that turns the schedule on and
off, and it shows the next execution time.
Turn a schedule off before you change its version or its profile. Those two fields are locked while
the schedule is enabled.
Cron presets
The editor offers presets. They cover intervals from every minute up to every 12 hours, and longer. Build a custom expression in the same editor by picking minutes, hours and weekdays. The editor prints the expression back in words, so you can check it.What a tick fires
A schedule works in one of two modes.One execution per tick
This is the default. Each tick starts one execution of the workflow. The execution uses the schedule’s inputs, its pinned version, and its profile or pool. The execution appears in the workflow’s Executions list like any other run, withScheduled as its
runner. Filter for these runs with triggerSource=schedule:
A batch per tick
Point the schedule at a Google Sheet and each tick creates a whole batch instead of one execution. The platform re-reads the tab on every tick, so the batch matches the rows that exist at that moment. Add rows during the week and next week’s run picks them up.
A new recurring batch paces by concurrency alone. It caps how many rows run at the same time, and each
time one finishes the next starts. Every batch from one schedule shares that one budget, so two
overlapping ticks cannot double the load.
Book a single execution
For a one-off, use the workflow’s Run panel. Set a date and time under Schedule, then start the run. The time must be in the future. The execution waits in the Scheduled Executions view until its time arrives.Scheduled executions
The Scheduled Executions view lists every execution the platform holds for this workflow. That covers one-off bookings and every row of every batch.
Sort the list by scheduled time, and filter it by status or by batch. Each row has two actions:
Cancel, which stops it starting, and Reschedule, which moves it to a new time.
A row that reaches
triggered becomes an ordinary execution, with its own ID, status, recording and
result. From that point it behaves like any other run. See
Executions and statuses.
Best practices
Decide whether to pin the version
Decide whether to pin the version
Published version follows your latest publish, which means a publish changes what runs. This is usually what you want, as it means that new updates are incorporated into your next executions.
Use a profile pool when your workflow logs in somewhere
Use a profile pool when your workflow logs in somewhere
Rows that run at the same time under one profile share one browser state and can cause side effects. A profile pool gives each row its browser session and optionally login details, which can be useful if the portal you’re automating doesn’t react well to having one set of credentials used 100 times concurrently. See Agent profiles.
Send the results somewhere
Send the results somewhere
Attach a webhook or a Slack notification so a failure reaches a
person. See Webhooks and Slack.
Next
Batch executions
Pacing, column mapping, and batch statuses
Executions and statuses
What an execution does once it starts
Webhooks and Slack
Get told when a unattended execution fails
Versions and publishing
What “published version” tracks