Flow Orchestration
Flow Orchestration is the Salesforce feature for sequencing multi-step, multi-user business processes on top of Flow Builder.
Definition
Flow Orchestration is the Salesforce feature for sequencing multi-step, multi-user business processes on top of Flow Builder. Where a single flow handles automation that runs end-to-end for one user or one record, an Orchestration chains many flows together across stages, assigns work to different users at each step, and waits for each step to finish before moving on.
Built into Flow Builder under the Orchestrator trigger type, an orchestration is itself a flow definition. Each stage holds one or more steps; each step calls either an autolaunched flow (background work) or a screen flow (a task assigned to a user or queue). Steps within a stage can run in parallel; stages run sequentially. Salesforce launched Flow Orchestration in Winter 22 and made it generally available with no extra license cost in Summer 23.
Why orchestration exists alongside plain flows
Stages and steps, the orchestration anatomy
An orchestration is a hierarchy of stages and steps. A stage is a logical phase like Underwriting Review or Customer Onboarding. Each stage contains one or more steps, and each step calls a flow. Steps within a stage run in parallel; stages run in strict sequence and the next stage starts only when every step in the current one finishes. Stages also have entry and exit conditions, so a stage can skip itself when the data does not meet the criteria.
Interactive vs. background steps
Background steps invoke an autolaunched flow and run without a UI. Interactive steps invoke a screen flow and assign work to a user or queue. Interactive steps show up in the assignee's My Work list under the Orchestration Work Guide component, which embeds inside a record page or app page. The assignee opens the work, completes the screen flow, and the orchestration progresses.
The Work Guide component
Orchestration Work Guide is the Lightning component that surfaces assigned work to end users. Drop it on a record page (most often Account, Case, or a custom object), and any user with assigned interactive steps for that record sees a checklist of tasks. The component handles launching the screen flow, capturing the response, and marking the step complete. Without it, users have nowhere to do their work.
Record-triggered and autolaunched orchestrations
Two trigger types exist. Record-triggered orchestrations fire when a record meets the trigger criteria, the same way record-triggered flows do. Autolaunched orchestrations run when called from Apex, REST, a parent flow, or another orchestration. Pick the trigger based on whether the start event lives on a record or comes from elsewhere in the system.
Reassignment and SLAs
Each interactive step can be reassigned by the current assignee, by an admin, or automatically by an exit-condition formula on the step. Assignments target users, queues, or groups. Orchestration does not ship a built-in SLA timer, but admins build escalation by combining a scheduled-path on the original record with a reassignment action when an SLA breaches.
Monitoring and run history
Salesforce ships an Orchestration Runs object that tracks every orchestration instance, the stage and step state, the assigned user, and the timestamps. Build list views and reports on Orchestration Runs to track throughput, identify stuck stages, and audit completion. The Orchestration Console (in Setup) gives admins a view of all running orchestrations with the ability to advance, restart, or cancel any of them.
When orchestration is the right tool
Use Flow Orchestration when work hops between teams, the process has clear stages with handoffs, and steps need to wait on human input. Use a single screen flow when one user completes the whole process in one sitting. Use a record-triggered flow when no human input is needed. Forcing every approval chain into orchestration overcomplicates simple workflows.
Build a multi-stage record-triggered orchestration
Orchestration setup follows the same Setup, Flows entry point as any flow. The difference is the trigger and the canvas layout.
- Create the source flows first
Build every autolaunched and screen flow that the orchestration will call. Each step calls a flow, so the flows must exist before the orchestration can reference them.
- New Flow with Orchestrator trigger
Open Flow Builder, click New Flow, choose Orchestrator, then Record-Triggered Orchestration or Autolaunched Orchestration. Record-triggered orchestrations need the object and trigger event configured.
- Add stages and steps
Drop stages onto the canvas in sequence. Inside each stage, add background steps (which call autolaunched flows) or interactive steps (which call screen flows and need an assignee).
- Configure assignments
For each interactive step, set the assignee. Choose a specific user, a queue, a public group, or a formula that resolves to one of those. Set the step label that the user sees in the Work Guide.
- Drop the Work Guide on relevant Lightning pages
Edit the record page (Account, Case, custom object). Add the Orchestration Work Guide component to a region where assignees will see it. Save and activate the page.
- Activate and monitor
Save the orchestration, activate the version, and verify it fires by creating or editing a record that meets the entry criteria. Check Setup, Orchestration Runs to see the live instance.
- The Work Guide component is the only way users see their assigned interactive steps. Skipping it during page layout configuration is the most common reason new orchestrations look broken.
- Steps inside a stage run in parallel, which means there is no ordering guarantee for background steps. If a background step depends on data created by another step, put them in separate stages.
- Reassignments do not transfer record ownership or sharing. Make sure the new assignee already has access to the underlying record, or the screen flow will fail at runtime.
- Orchestration Runs persists indefinitely. Old runs can clutter reports. Build a cleanup process or archive periodically.
Trust & references
Cross-checked against the following references.
- Flow OrchestrationSalesforce Help
- Build a Flow OrchestrationSalesforce Help
Straight from the source - Salesforce's reference material on Flow Orchestration.
- Orchestration Work Guide ComponentSalesforce Help
- Orchestration Runs ObjectSalesforce Developers
About the Author
Dipojjal Chakrabarti is a B2C Solution Architect with 29 Salesforce certifications and over 13 years in the Salesforce ecosystem. He runs salesforcedictionary.com to help admins, developers, architects, and cert/interview candidates sharpen their fundamentals. More about Dipojjal.
Test your knowledge
Q1. What does Flow Orchestration do?
Q2. What scenarios suit Flow Orchestration?
Q3. How does Flow Orchestration build processes?
Discussion
Loading discussion…