Scheduled flows and screen flows

What is a scheduled flow?#

A scheduled flow runs on the server at the hour you choose: it works with nobody in the app and every browser closed. It scans all records of the chosen object and applies its actions to those matching the condition. Build one from Setup > Flows > + New Flow > Scheduled Flow.

Setup steps#

1. Start node: pick the object and the hour (Türkiye time). The frequency is daily and the hour is a full hour between 00:00 and 23:00.
2. Condition Check: the same field catalogue and operators as record-triggered flows. Date fields gain three more: before today (past), within the next X days and older than X days.
3. Actions: there is a single branch, and its action sequence runs for every matching record. Scheduled flows have no Not met branch and no scheduled paths.

Once per record#

A scheduled flow does not fire repeatedly for the same record. Once a record has matched and received the actions, it is not processed again the next day. If the record stops matching and later matches again, it fires again. This is what keeps overdue invoices from generating a fresh task every single morning.

Running by hand and the last run#

Active scheduled flows show a Run Now link for administrators in the flow list: it starts the scan without waiting for the hour. The Last run column shows the time of the last scan, how many records matched and how many actually ran. The same information lands in the Run History card below, with the source shown as Scheduler.

Screen flows#

A screen flow is a wizard that walks the user through a form and creates a record at the end. Nothing triggers it automatically: the user picks it from the ＋ Quick Create menu, the wizard opens, a progress bar shows the current step, Back and Next move between screens, and Finish on the last step creates the record.

Its setup is three cards:

1. Target: which record the wizard creates at the end. The options are Lead, Case, Task and Opportunity.
2. Screens: name each screen and add fields from the catalogue for that target. Required fields are marked with a star and the wizard will not finish without them. You may add as many screens as you like.
3. Finish: the message shown once the record is created.

On the Opportunity target the Account field is a lookup: the user picks from your existing accounts, so the opportunity lands on the right account. Fields left blank get sensible defaults: a lead's status becomes New, a case's priority becomes Medium, a task is due tomorrow, and an opportunity opens at your first stage with a close date 30 days out.

Comparing the flow types#

The flow did not run: what to check, in order#

1. Is it active? Look at the checkbox in the first column of the flow list. Inactive flows carry a badge.
2. Is the condition truly met? Use Preview Matches on a scheduled flow, or read the summary lines on the condition node of a record-triggered one. A frequent mistake: an "equals" value that does not match the picklist value character for character.
3. What does Run History say? If the flow is absent from the list it never triggered. If it is there with Error, it ran but an action failed.
4. What was the source? If the record arrived through the API or a web form, Run History shows the source as API or Web form. Server-only actions (Push Notification, Send Email, Call Webhook) may not be visible in the UI immediately, but they appear in the history.
5. Is a scheduled path still waiting? A path whose reference date is already in the past never fires, and a record that fails the re-check is skipped.

For every node on the canvas see The flow canvas, and for the map of automation tools see Automation.