Go back to flow logic
-
- UpdatedFeb 7, 2025
- 3 minutes to read
- Washington DC
- Flow Designer
Return to a prior step in the flow to repeat a sequence of actions.
Family release requirements
You can only add Go back to flow logic to new flows created from the Washington DC family release and forward. Flows that were created in versions prior to the Washington DC family release do not support Go back to flow logic.
Valid Go back to placement
- The Go back to flow logic must be within a branch of a parent flow logic block.
- Then branch of If, Else If, or Else flow logic
- Answer branch of Make a decision flow logic
- Catch branch of Try flow logic
- The Go back to flow logic must be outside of the Error handler section.
Valid Go back to target step
- The target must be a step before the Go back to flow logic.
- The target can't be a step within a different branch of the flow.
- The target can't be a step within the same branch as the Go back to flow logic.
- The target can't be a step within a non-branching flow logic block unless the non-branching flow logic block also includes a child Go back to flow logic.
- The target can be a step outside of a non-branching flow logic block except for Do the following in parallel flow logic.Warning: Selecting a target step outside of a parent flow logic block exits the current loop and resets its loop iteration count. The system displays separate loop iteration counters for the Go back to loop and the parent flow logic block. All loops are limited by the maximum number of loop iterations property (sn_flow_designer.max_iterations).
Inputs
| Input | Description |
|---|---|
| Go back to step | Step in the flow that meets the conditions of a Go back to step target. |
Example: Go back to start of flow
In this example, the flow goes back to the first step when the approval task for the trigger record is rejected. Valid Go back to targets include steps 1, 2, and 3. Step 4 violates rule 2 as it's a step within a different branch. Steps 5 and 6 violate rule 3 in that they're steps within the same branch of the flow.
Outputs
This flow logic has no outputs.
General guidelines
Use these general guidelines when adding Go back to flow logic.
- Add Go back to flow logic after the flow structure is complete
- Go back to flow logic depends on a fixed sequence of steps to function properly. Wait to add Go back to flow logic until the flow has valid target steps.
- Avoid creating duplicate Go back to steps
- A flow uses the first Go back to flow logic whose conditions are met. The flow ignores all Go back to flow logic steps after the first.
- Avoid creating infinite loops
- Specify a condition to resume the flow or to throw an error with each Go back to loop. Error and resume conditions prevent a flow from running until it reaches the maximum number of loop iterations (sn_flow_designer.max_iterations property). You can use an If flow logic to check for loop end conditions. For example, create a flow variable that counts how many times the flow has run the Go back to flow logic. When the flow variable reaches a limit, end the flow.
- Delete Go back to flow logic to move it
- After you add Go back to flow logic, you can't move it to another location. You can only delete it from its current location and then add it to another valid location.
On this page
Related Content
- Assign subflow outputs flow logic
Specify the data the subflow returns when it completes running. Use subflow output as data for a parent flow or as input for another process.
- Call a workflow flow logic
Run a published and active workflow from your flow. You can use the flow data as a workflow input. For example, you can specify the current record as a workflow input.
- Do the following until flow logic
Apply one or more actions repeatedly until an end condition is met. You can use the flow data to specify the end conditions.
- Do the following in parallel flow logic
Run actions and subflows in separate paths within an isolated flow logic block.
- Dynamic flows flow logic
Identify and run a flow or subflow dynamically by using runtime data. Build templates to provide expected inputs for dynamically called flows or subflows.
- End Flow flow logic
Stop running the current flow. Use End Flow within a branch of the flow to specify an exit condition. For example, end the flow when it reaches a specific If flow logic block.
- Exit Loop flow logic
Exit from a flow logic loop when the conditions of an If flow logic are met. Continue running the flow from the next step after the flow logic loop. This flow logic is also known as break.
- For Each flow logic
Apply one or more actions to each record in a list of records.
- If flow logic
Selectively apply one or more actions only when a list of conditions is met.
- Make a decision flow logic
You can use the decision table branching logic in situations where multiple conditional paths are required, as an alternative to nested If, Else If, or Else flow logic. For example, if you want to determine what kind of car insurance you need, you can add inputs such as your age, accident history, and car model to the decision table to determine a level of insurance coverage. This logic can save you time and present a more readable format than nested if conditions or switch case statements.
- Set Flow Variables flow logic
Assign a value to one or more flow variables, which store flow data as data pills. Access flow variable values by referring to their data pill.
- Skip Iteration flow logic
Skip the current iteration of a flow logic loop when the conditions of an If flow logic are met. Continue running the flow logic loop with the next item in the list. This flow logic is also known as continue.
- Try flow logic
Allow a flow to continue running when an error occurs within a flow logic block. Run a sequence of actions in response to errors within the flow logic block.
- Wait for a duration flow logic
Use this flow logic to give your users time to act during automated processes or to wait for a specific date and time to complete actions.