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.