What Flow Orchestrator Is
Flow Orchestrator is Salesforce’s tool for multi-user, multi-step, long-running processes — something that takes days or weeks, passes between different roles, and requires human approvals or input along the way.
Regular Flow is transactional. It executes end-to-end in one session or one automated trigger. It doesn’t wait for a human two departments away to approve something three days later.
That’s the core difference. Everything else follows.
The Shape of an Orchestration
An orchestration is a sequence of stages. Each stage contains one or more steps. Each step is either:
- An interactive step — a screen flow assigned to a user, queue, or public group. The orchestration pauses until the user completes it.
- A background step — an autolaunched flow that runs automatically without human input.
Stages run sequentially. Steps inside a stage can run in parallel if they don’t depend on each other.
This model makes it natural to express business processes that span teams: Sales completes stage 1; Legal completes stage 2; Finance completes stage 3; each stage has one or more tasks.
When Orchestrator Is the Right Tool
Use Orchestrator when the process spans days or weeks.
A loan approval that routes from applicant to underwriter to compliance to funding — days or weeks of elapsed time, different users at each stage. Orchestrator fits.
Use Orchestrator when multiple users act on the same record in a defined order.
A content publishing workflow where the author drafts, an editor reviews, legal approves, and marketing publishes. Each role has their own screen flow; the orchestration tracks progress.
Use Orchestrator when parallel work needs to converge.
A product launch coordination where engineering, marketing, and sales complete independent tasks before a final “ready to launch” gate.
When Regular Flow Is Right
Use Flow when the process is transactional.
A user submits a form, data is validated, records are created or updated, an email goes out, and the transaction ends. All in one session. Flow.
Use Flow when automation runs without human input.
Record-triggered logic, scheduled batch updates, integration callouts. Flow.
Use Flow when the “multi-step” is really one user in one sitting.
A wizard that walks a user through 10 screens and commits at the end is a Screen Flow, not an orchestration. Orchestration is overkill for single-user, single-session work.
Side-by-Side Comparison
| Concern | Flow | Flow Orchestrator |
|---|---|---|
| Session | Single | Multi-session, persistent |
| Users | Typically one | Multiple, across stages |
| Duration | Seconds to minutes | Hours to weeks |
| Approvals / handoffs | No | Yes |
| State persistence | In-memory | Persisted in Orchestration Work Item |
| Record triggering | Yes (record-triggered, scheduled, etc.) | Indirectly — launched by a flow |
| Debug / audit | Debug log | Orchestration Run history |
| License | Included | Requires Orchestrator license in most editions |
Licensing Reality Check
Flow Orchestrator is not free in every edition. Older orgs have Orchestrator included; newer orgs may require a separate Runs pack. Before committing to Orchestrator for a new process, confirm your org has the entitlement.
Orchestration runs are metered. Each completed orchestration consumes a run. High-volume processes should be costed carefully.
Common Mistakes
Building an orchestration for a single-user form. Tempting because “it has multiple steps,” but if all steps are one user in one sitting, Screen Flow is simpler.
Building a flow with long delays to simulate orchestration. “Pause” elements in flow are limited — they use either a time-based wait or platform event. They don’t persist gracefully across days of real-world time.
Skipping the pause/resume semantics. Orchestration steps can be reassigned, escalated, and reminded. If you don’t use these features, you’re paying for Orchestrator’s overhead without its benefits.
Practical Example: Employee Onboarding
A realistic orchestration:
- Stage 1: New hire form. HR fills out a Screen Flow with employee details. Record gets created.
- Stage 2 (parallel):
- IT provisions laptop and accounts (Screen Flow for IT).
- Facilities assigns desk (Screen Flow for Facilities).
- Finance sets up payroll (background flow calling external API).
- Stage 3: Manager approval. Manager reviews everything via a Screen Flow and signs off.
- Stage 4: Welcome email. Background flow sends the welcome package.
Three of these stages have human gates. Two have parallel work. One spans multiple days. This is what Orchestrator was built for.
Debugging Orchestrations
Orchestration runs have their own debugging surface. Open Setup → Orchestration Runs to see:
- Active orchestrations and their current stage.
- Completed stages and durations.
- Failed steps with error context.
- Work items pending user action.
Within each step, regular flow debugging applies. The run history gives you the macro; per-step logs give you the micro.
Migration from Approval Processes
Salesforce’s legacy Approval Processes do some of what Orchestrator does, but with less flexibility. If you’re on approvals today and considering a rewrite:
- Simple, single-step approvals are fine to leave on legacy Approval Processes.
- Multi-stage, branching, or parallel-track approvals benefit from Orchestrator.
- Heavy reliance on approval emails with inline approve/reject is a current Orchestrator gap — Salesforce is improving this, but verify feature parity before migrating.
Frequently Asked Questions
Can an orchestration invoke a flow?
Yes — background steps are autolaunched flows. Interactive steps are screen flows. Composition works in both directions.
Can a flow invoke an orchestration?
Yes, via an invocable “Launch Orchestration” action.
How do I test an orchestration end to end?
Create test users representing each role, run the orchestration in sandbox, and complete steps as each user. There’s no single-click debug mode spanning all steps.
Is there a visual runtime view for end users?
Users see their assigned work items in the standard work guide component or via notifications. There’s no out-of-the-box “show me the whole process” view for non-admins — you’d build that as a custom Lightning page.