--- sourceDocument: Brazil Build workflows sourceDocumentLink: https://www.servicenow.com/docs/r/build-workflows Release : - brazil ft:locale : - en-US ft:publication_title : - Brazil Build workflows ft:clusterId : - crworkflow bundleId : - crworkflow workflow : - Creator --- # Go back to flow logic # Go back to flow logic {#ariaid-title1} Release version: Brazil Updated September 10, 2026 ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 3 minutes to read Summarize ![AI sparkle icon](https://servicenow.com/docs/portal-asset/ai-sparkle-icon) Summarized using AI This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete. ## Summary of Go back to flow logic "Go back to flow logic" enables you to return to a prior step within a flow to repeat a sequence of actions. This functionality is available only for flows created from the Washington DC family release onward and is intended to support looping behavior within flows while maintaining control over iteration limits. Show full answer Show less ## Placement and Usage Requirements * **Release compatibility:** Only supported in flows created with the Washington DC release or later. * **Valid placement:** Must be added inside branches of parent flow logic blocks such as Then branches of If/Else If/Else, Answer branches of Make a decision, or Catch branches of Try logic. It cannot be placed inside Error handler sections. * **Valid target steps:** The step you return to must be earlier than the Go back step, not within the same branch or a different branch of the flow, and must meet specific restrictions related to non-branching blocks and parallel execution. Returning to a target outside the current parent block will exit the loop and reset iteration counts. ## Inputs and Behavior * **Input:** Select a valid prior step in the flow as the target to return to. * **Example:** Returning to the start of the flow when an approval task is rejected, ensuring only valid steps are targeted to avoid rule violations. * **Loops:** Loop iterations are tracked separately for the Go back loop and its parent flow logic block, limited by the `snflowdesigner.maxiterations` property to avoid infinite loops. ## General Guidelines * Add Go back to flow logic only after the flow structure is finalized to ensure valid target steps. * Use the first Go back logic whose conditions are met; subsequent Go back steps are ignored. * Implement conditions to prevent infinite loops by defining criteria to resume or throw errors, such as using counters and If logic to detect loop limits. * To relocate Go back logic, you must delete it and re-add at the new valid location as it cannot be moved directly. ## Related Flow Logic This logic integrates with other flow constructs such as Assign subflow outputs, Call a workflow, If, Make a decision, Try, and looping constructs like Do the following until, Exit Loop, and Skip Iteration, enabling robust flow control and error handling. Return to a prior step in the flow to repeat a sequence of actions. ## Family release requirements {#go-back-to-flow-logic__section_zlr_xhb_t1c} 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 {#go-back-to-flow-logic__id_ry3_tfq_twb} You can only add Go back to flow logic within certain portions of a flow. * 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 {#go-back-to-flow-logic__ul_v33_2hb_twb} * The Go back to flow logic must be outside of the Error handler section. {#go-back-to-flow-logic__ul_thb_ggb_twb} ## Valid Go back to target step {#go-back-to-flow-logic__id_zmr_tfq_twb} Go back to flow logic only allows you to select a valid return target step. A valid target step must meet all of these conditions. 1. The target must be a step before the Go back to flow logic. 2. The target can't be a step within a different branch of the flow. 3. The target can't be a step within the same branch as the Go back to flow logic. 4. 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. 5. 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). {#go-back-to-flow-logic__ul_gj1_bgw_qwb} ## Inputs {#go-back-to-flow-logic__section_y1y_lgq_twb} {#go-back-to-flow-logic__table_kb3_pgq_twb__entry__2} | Input | Description | |-|-| | Go back to step | Step in the flow that meets the conditions of a Go back to step target. | [ ] {#go-back-to-flow-logic__table_kb3_pgq_twb} ## Go back to start of flow {#go-back-to-flow-logic__example_qzy_2hq_twb} 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 {#go-back-to-flow-logic__section_kkm_dbj_1xb} This flow logic has no outputs. ## General guidelines {#go-back-to-flow-logic__id_q31_5fq_twb} 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. **Related concepts** * [Assign subflow outputs flow logic](https://www.servicenow.com/docs/qX27EulT5kOBRGKBYxAG8A "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](https://www.servicenow.com/docs/NQEIJIgXEakKk3tuRLtZPw "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](https://www.servicenow.com/docs/ovrNT5MVtXPVysCc2ZtXzw "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](https://www.servicenow.com/docs/fHNODu_WWcW9BSU~UR9nUw "Run actions and subflows in separate paths within an isolated flow logic block.") * [Dynamic flows flow logic](https://www.servicenow.com/docs/UPiveOIQepWbt3_pM56DDQ "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](https://www.servicenow.com/docs/yoHSXT_u6_hZ~2BZ7Vs2sQ "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.") * [For Each flow logic](https://www.servicenow.com/docs/esmLMDyz1JByfBNkIp58zw "Apply one or more actions to each record in a list of records.") * [If flow logic](https://www.servicenow.com/docs/DdLyuPtduXTkT6w~M7dtvg "Selectively apply one or more actions only when a list of conditions is met.") * [Make a decision flow logic](https://www.servicenow.com/docs/8NnG8rZdZCenxcQACsoXIQ "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](https://www.servicenow.com/docs/pznT35Am0Xun~TcL09vXNg "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.") * [Try flow logic](https://www.servicenow.com/docs/EfEGiwtJuz7RzLyjvwwBJA "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](https://www.servicenow.com/docs/2GOH3wSHrDcPpajWzQTdAg "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.") **Related reference** * [Append to Flow Variables flow logic](https://www.servicenow.com/docs/JlnmAl1y4IYNT_kgYbTTBg "Append a value to one or more array of objects flow variables. Use flow data to generate values.") * [Exit Loop flow logic](https://www.servicenow.com/docs/IGMuJBwBeRK~eUyPdIpFIQ "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.") * [Get Flow Outputs flow logic](https://www.servicenow.com/docs/fXxlC3vf5PmIAASLlaHC7w "Retrieve output values generated by dynamic flows or subflows.") * [Skip Iteration flow logic](https://www.servicenow.com/docs/fvFzdxlhfu7NJl3i~niFcQ "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.")