Screen Flow versus Autolaunched Flow (No Trigger)
Key Takeaway
Ask first whether the user needs to see or enter anything. If so, use a Screen Flow. If the work runs in the background after a person or code starts it, use an Autolaunched Flow (No Trigger).
Screen Flow and Autolaunched Flow (No Trigger) are two flow types that start only when something launches them, but they differ on whether a person takes part. A Screen Flow shows screens that guide a user, collect input or display information. An Autolaunched Flow (No Trigger) does its work in the background with no user interaction.
How the two flow types differ
A flow's type controls which elements and resources you can add and how you can distribute the flow, so picking the flow type is a design decision, not just a label.
| Screen Flow | Autolaunched Flow (No Trigger) | |
|---|---|---|
| What it does | Guides users through a business process | Does its work in the background |
| User interaction | Required, because it includes screens, local actions, steps, choices or dynamic choices | None |
| Doesn't support | Wait elements | Screens, local actions, choices or choice sets |
Some building blocks belong to one flow type only:
- You can add a Choice resource only in a Screen Flow.
- You can add a Custom Error element only in a record-triggered flow.