---
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


---

# Troubleshoot a flow

# Troubleshoot a flow {#ariaid-title1}

Release version: Brazil  
Updated September 10, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 3 minutes to read  
Analyze a failed flow to check for data issues, identify potential conflicts, and receive targeted recommendations to resolve the error.

## Before you begin

* Role Required: sn_troubleshoot.flow_troubleshooting_agent_user to access the Flow Troubleshooting Agent
* Role required: The flow_designer or flow_admin role to access the flow execution details page
* A flow execution that has an error or requires diagnosis
* ServiceNow Otto enabled in your instance. For setup instructions, see [Overview tab in AI Admin Hub](https://www.servicenow.com/docs/access?context=configuring-now-assist&version=brazil&pubname=brazil-intelligent-experiences&ft:locale=en-US).
{#troubleshoot-a-flow__ul_jd2_gsw_3kc}

## About this task

When a flow produces an error or unexpected results during execution, the Flow Troubleshooting Agent provides conversational debugging to help you understand what went wrong. The agent analyzes flow steps, data
transformations, and checks for conflicts with business rules or other workflows.

## Procedure

1. Navigate to AllProcess AutomationWorkflow StudioOperationsFlows {#troubleshoot-a-flow__troubleshoot_flow_from_execution_details}
{#troubleshoot-a-flow__troubleshoot_flow_from_execution_details}
2. Navigate to MonitoringAll Executions.
3. Open the flow execution details that you want to troubleshoot.  
4. Select Troubleshoot to open ServiceNow Otto.  
5. Open the Flow Troubleshooting Agent.  
   Select the Troubleshoot Flow button at the top of the flow execution details page to launch the agent.

   Alternatively, select the ServiceNow Otto button from any screen and request access to the Flow Troubleshooting Agent.
   {#troubleshoot-a-flow__troubleshoot_flow_from_otto_button}
{#troubleshoot-a-flow__troubleshoot_flow_from_otto_button}
6. Describe the issue you're experiencing with your flow, or ask the agent to analyze the failed execution.  
   {#troubleshoot-a-flow__troubleshoot_flow_from_workspace}
{#troubleshoot-a-flow__troubleshoot_flow_from_workspace}
7. Review the agent's flow summary.  

   The agent provides a summary of your flow steps, their purpose, and their sequence. This helps you understand the context and identify where the failure might have occurred.
8. Analyze the data used and generated by each step.  
   The agent analyzes and displays the data flowing through each step in your flow. Review:
   * Input data to each step
   * Data transformations and mappings
   * Output data produced by each step
   * Any data validation errors or missing values
   {#troubleshoot-a-flow__ul_md2_gsw_3kc}
9. Identify potential conflicts with business logic.  

   The agent scans for and reports potential conflicts with:
   * Other workflows or flows that may be running against the same data
   * Business rules that might be triggered by your flow's actions
   * Field-level security or ACL restrictions that could block data access
   * Integration configurations or API limits that might affect external actions
   {#troubleshoot-a-flow__ul_nd2_gsw_3kc}
10. Review the agent's recommendations.  

    The agent provides specific, evidence-based actions you can take to resolve the error. Each recommendation includes:
    * The recommended action or fix
    * The evidence or reasoning behind the recommendation
    * The potential impact of implementing the recommendation
    {#troubleshoot-a-flow__ul_od2_gsw_3kc}
11. Edit the flow or other workflow business logic to apply recommendations.  
    Based on the agent's suggestions, make changes to your flow, business rules, or configurations. Return to the flow designer or relevant configuration page to implement the fix.

    After making changes, run your flow again to verify that the error is resolved. If needed, return to the Flow Troubleshooting Agent to continue the analysis with new execution data.
{#troubleshoot-a-flow__steps_ld2_gsw_3kc}

## Result

You have successfully used the Flow Troubleshooting Agent to diagnose your flow error, identify potential conflicts, and apply targeted recommendations to resolve the issue.

## Example: Troubleshooting a failed approval action {#troubleshoot-a-flow__example_qd2_gsw_3kc}

You have a flow that creates an approval record but the approval is not sending notifications. You:

1. Navigate to the failed flow execution and select Troubleshoot.
2. The agent summarizes your flow steps and identifies the approval action that failed.
3. The agent analyzes the data sent to the approval action and finds that the `recipient` field is empty.
4. The agent identifies a potential conflict: a business rule is clearing the recipient field before the approval sends.
5. The agent recommends reordering your flow steps to map the recipient field after the business rule runs, or modifying the business rule to exclude your flow's records.
6. You implement the recommended fix and re-run your flow; the approval now sends successfully.
{#troubleshoot-a-flow__ol_rd2_gsw_3kc}

## What to do next

Test your flow to determine if the issue is resolved.

*[\>]: and then