Schedule a workflow

The Start node holds the schedule configuration. Configure it, run the workflow manually, then activate the schedule when the result is correct.

Choose when it runs#

• Once: run when you start the workflow manually.
• Interval: repeat every configured number of seconds, minutes, hours, or days. Start immediately or from a configured first-run time.
• Daily times: run at one or more times of day, using 24-hour values such as 09:00 and 17:30.

Daily times use the executing runtime’s local clock and timezone. Confirm the device timezone when the runtime is on another machine or when daylight-saving changes matter.

Keep the runtime available#

Browser scheduling depends on the app and browser remaining available. Desktop or Extension scheduling depends on its runtime remaining available. Saving to your account is not an always-on cloud deployment.

Do not depend on missed occurrences being replayed after a runtime is unavailable. On resumption, scheduling advances to an upcoming occurrence rather than replaying a backlog.

Configure before activation#

Choose the runtime, complete connection setup, check Test mode, and manually inspect a successful run before activating. A scheduled workflow should not depend on a file picker or another interactive prompt that nobody will answer.

Deactivate the schedule before changing settings that the app locks during active execution. Use the library’s workflow status to confirm whether a schedule is active.

Sharing does not activate a schedule#

Workflow exports retain the Start node’s schedule settings, but they do not transfer an active schedule or a runtime deployment. The reader imports an inactive copy and chooses whether to activate it.

For a pause within one run, use Wait. For persistent progress between scheduled runs, use State.