Steps are grouped in stages and can be run sequentially, concurrently, or when
specified requirements are met. Approval 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.
Note The Step resource in Flow Approval
Processes isn't related to the discontinued Step element in flows.
Status
When an orchestration run associated with an approval submission 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
The approval step met its exist condition
The background step's flow was completed.
The step was completed when its associated stage encountered an error.
Discontinued
The step was in progress when its associated stage completed.
The step was in progress when the orchestration run associated with the
approval submission encountered an error.
The step was in progress when its associated stage encountered an error.
Error
The step encountered an error.
The autolaunched flow associated with a background step encountered an
error.
The screen flow associated with an approval step encountered an error.
Approval Steps Approval steps require user interaction and create approval actions that assigned approvers or delegates can complete asynchronously. Approvers can complete reviews without running the associated flow, so include only actions directly relevant to the approval work item. Use a background step after the approval step to update related records or trigger additional notifications.
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. Use background steps to carry out actions that are related to an approval submission but aren’t part of an approval work item. For example, use a background step to update records or trigger additional notifications related to the approval.
Did this article solve your issue?
Let us know so we can improve!
Loading
Salesforce Help | Article
Cookie Consent Manager
General Information
Required Cookies
Functional Cookies
Advertising Cookies
General Information
We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required Cookies
Always Active
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional Cookies
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising Cookies
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.