Set how often a process runs

Updated 19 October 2026 · For back office users

A process doesn't run on a fixed clock. Instead, each run schedules the next one when it finishes. Schedule Period Minutes sets the gap, and Continue Schedule On Failure decides whether a failed run still schedules the next.

Schedule Period Minutes

Enter how many minutes after a run finishes the next run should start. For example, 60 for hourly or 1440 for daily.
Leave it empty, or set it to 0, and the process runs only when someone schedules it. The Overview tab shows this as Runs once.
The gap is counted from when the run finishes, which includes every record's steps. So the start time can drift a little later over time. Check the Next run column on the dashboard to see when it's due.
If the process uses a Schedule Expression to delay records, the run isn't finished until the last delayed record has been handled, so the next run waits for that too.

Starting the schedule

Publishing a process doesn't start it. A back office user starts the first run from the Jobs tab using Schedule a job. From then on, each run schedules the next.

Each run schedules its own next run, so scheduling an extra job while a next run is already scheduled starts a second, parallel cycle. Check the Jobs tab for an existing Run Process job first.

What counts as a failed run

The process couldn't fetch its records, for example because the data source returned an error or a setting is missing.
Every record that was fetched failed.
Something else went wrong partway through, such as a Schedule Expression problem.

A run where only some records failed is shown as Partial. It isn't a failure, and the next run is scheduled as normal.

Continue Schedule On Failure

Off (the default): after a failed run, no next run is scheduled. Someone needs to fix the problem and start the process again, for example with Requeue on the History tab or a new job on the Jobs tab.
On: a failed run still schedules the next run Schedule Period Minutes later, as if it had succeeded.

The Overview tab shows the setting as Continue on failure: Yes or No.

Temporary data source errors

If the data source answers with a 400 (Bad Request) error when the records are fetched, and the process has a schedule period, AutomatedOn doesn't treat it as a failure. It marks the run Retry scheduled and tries again after 60 minutes, or after the schedule period if that's longer. This happens whatever Continue Schedule On Failure is set to.