Put it on a schedule

Your flow works when you press Test run. Now let's make it run by itself every morning, tell you when something goes wrong, and show you how to fix a failed run. We use the Save stories flow from the earlier guides, but the steps are the same for any flow.

In short: add a Schedule trigger, set the flow's Timezone, press Publish, then watch it in Operate › Runs and the bell.

Step 1: Add a Schedule trigger

A flow can have more than one trigger. Keep Manual for your own tests, and add a schedule next to it.

1. Open the flow in Studio › Flows.
2. Press Add node (+) in the canvas controls (bottom left), search schedule and pick Schedule.
3. Set Unit to days, Every to 1, and At (HH:MM, flow timezone; days only) to 08:00.
4. Drag from Schedule's Next dot onto Open URL's input dot. Both triggers now lead into the same steps.

Other schedules:

Step 2: Set the timezone

08:00 means 08:00 in the flow's timezone, which is UTC until you change it.

1. Open the Settings window (right side of the editor).
2. Set Timezone to yours, like Asia/Jakarta.

Step 3: Make it safe to run alone

A schedule runs for real with nobody watching. Before you publish:

• Approvals: set If no answer to approve or reject with an after (ms). Otherwise the run waits for you until you answer, and the next morning's run has to wait behind it.
• Errors: on steps that can fail now and then (a slow page, a missing element), open Settings in the node's details and set On error, for example Retries 2 with a wait between them. Use Ask a human only where you'll be around to answer.
• A heads-up when it fails: in the flow's Settings, pick an Error flow. It's a flow that runs whenever this one fails, for example a Notify to your Discord.

Step 4: Publish

1. Press Publish (top right).
2. The button now shows Published v1.

The schedule runs the published version. Keep editing the draft as much as you like, because nothing changes for the schedule until you press Publish again (v2, v3…). Version history (the clock icon) keeps every publish. Use Make live on an older one to go back.

Step 5: Watch it run

Open any run to see it on its canvas, with each node's output and the logs as they were.

Step 6: Fix a failed run

1. In Operate › Runs, filter Status to Failed and open the run.
2. The failed node has a red ring. Open it: the Output and the Logs window show the error.
3. Fix the cause: a selector the site changed (), a sign-in that ran out (), a wrong value.
4. Press Retry from failed. It starts from the failed node and reuses what already worked. Pick With the current version to use your fix.
5. Press Publish so the schedule uses the fix too.

Going further: campaigns

A schedule runs one flow, in its own browser. When you want to run a flow for several accounts, each in its own signed-in browser with its own limits and a live dashboard, use a campaign: Operate › Campaigns. See .

FAQ

My schedule didn't start. Why?

Check three things: the flow is published (the button shows Published v…), the Schedule node is connected to the next step, and At is in the flow's Timezone, not yours. With days and At, it starts once that time has passed today, so publishing after 08:00 starts today's run within a minute.

Does the schedule pick up my latest edits?

Only after you press Publish. Schedules always run the published version.

Can a scheduled run post or buy for real?

Yes. Scheduled runs are real runs, so effect nodes (⚡) act. Try every change with Test run first, then publish.

How long are runs kept?

90 days. Rows you saved in tables stay until you delete them.