You are here:
Orchestration Steps
Steps are grouped in stages and can be run sequentially or concurrently. Interactive steps assign the completion of an active screen flow to a person, group, or queue and require user intervention. Background steps run an active autolaunched flow synchronously or asynchronously and have no user interaction. MuleSoft steps run an action imported from a MuleSoft operation and have no user interaction.
Required Editions
| View supported editions for Flow Orchestration. |
Automatic Output
At design time, automatic output resources are available throughout an orchestration, even before associated orchestration runs have access to the automatic output. This capability means that when you create an orchestration you must reference automatic output resources only when associated orchestration runs have access to it.
| Automatic Output | Run-Time Availability |
|---|---|
| Stage Status | After the stage is in progress |
| Step Status | After the parent stage is in progress |
| Flow Output Variable | After the parent step has been completed |
Status
When an orchestration is running, it manages the status for each step.
| Step run Status | Description |
|---|---|
| Not Started | The step hasn't met its entry condition. |
| In Progress | The step was started. |
| Completed |
|
| Discontinued |
|
| Error |
|
History
In history, a step in an orchestration has several possible milestones.
| Step Milestone | Description |
|---|---|
| Start Step | The step started. |
| End Step | The step was completed. |
| Discontinue Step |
|
| Fail Step | The step encountered an error. |
Flow Orchestration Step Run Record Ownership
For flow orchestration step run records created in Winter ’23 or later, the Owner ID field is set to the ID of the automated process user.
- Flow Orchestration Background Steps
A background step launches an active autolaunched flow and has no user interaction. You can control when a background step is ready to start. - Flow Orchestration Interactive Steps
An interactive step references an active screen flow and generates an orchestration work item. An assigned user completes the active screen flow in the Flow Orchestration Work Guide on the related record page. You can control when an interactive step is ready to start or when its status is set to completed. All interactive steps are processed asynchronously. - Flow Orchestration MuleSoft Steps
A MuleSoft step asynchronously runs an operation imported from a MuleSoft API and has no user interaction. You can control when a MuleSoft step is ready to start.

