By default, when a Flow Interview that uses screens finishes, a new interview for that Flow begins, and the user is redirected to the first screen of the Flow as noted in the Help on Flow Finish Behavior. The Standard "Complete" action on work steps has an undesired behavior on the "Status" field. The Flow is executed twice when launched through the Action Definition of a work step but not an issue if launched as a custom Quick Action or added through a Quick Action.
Information on ways to override this default behavior is available in the Help on Redirect Flow Users with a Local Action.
The Field Service Mobile App Flow when launched from the out-of-the-box "Complete" quick action by defining a type Flow in a work step template action definition, doesn't mark the status as Completed. Whereas the same Flow if added as a custom quick action in the action definition, the "Complete" action works fine and the work step is marked as Completed.
Field Service Flows execute twice when launched through the Action Definition of a Work Step because the standard "Complete" action triggers the default Flow Finish Behavior, which restarts the Flow upon completion.
There are two workarounds:
Option 1 — Use a Custom Quick Action instead of Action Definition: Add the Flow as a custom Quick Action in the Action Definition, rather than using the built-in Work Step Template Action Definition type. This bypasses the double-execution behavior and correctly marks the Work Step Status as Completed.
Option 2 — Add Finish Handling to an Aura Component: Add finish handling logic to an Aura component associated with the Flow. This allows you to override the default Flow Finish Behavior and prevent the Flow from restarting after completion. See the Additional Resources section for documentation on how to implement this.
000395255

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 are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security 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 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.