Flow Execution and Debugger

Each time a Flow executes, Auth0 stores an execution entry that you can use to review the Flow progress before, during, and after the execution. This is useful to debug errors in a Flow action or logic. 

To review an execution entry for a flow, follow the steps below:

1. Navigate to Auth0 Dashboard > Actions > Forms, then select Flows.

2. Select a Flow from the list. 

3. Select Executions.

Every execution entry has four properties:

• Execution date: The date of the flow execution.

• Execution ID: The unique ID of the flow execution.

• Status: The current stage of the flow execution. There are four possible execution statuses:

  • Pending: The execution just started.

  • Running: The execution is currently in progress.  

  • Completed: The execution finished without errors.

  • Failed: The execution failed due to an error, such as an action or logic error. To learn more about errors, review the Debug Flow Execution section. 

• View Details: Opens the debug window of the execution.

To help debug or troubleshoot a flow, you can review the flow’s Input, Output, and Error data. You can access this data through the View Details button available for each execution entry. 

There are two display modes available for reviewing execution details:

• Code: Displays raw code.

• View: Displays folded code.

Each flow’s execution details include the following information:

• Execution data: The unique ID of the flow execution.

• Action: A list of the actions in the flow.

• Status code: Third-party actions return a status code after execution that can be referenced in the third-party’s API documentation.

• Input: The data provided to the flow. Its structure is similar to a standard HTTP request.

  • Headers: The headers received in an HTTP request action that triggered the flow.

  • Body: An object that includes the payload received on invocation. For HTTP request actions, it corresponds directly to the request body. For any other action, it contains the field data entered by the user.

  • Metadata: An object that includes additional data of the user (e.g,. the client IP or user agent).

• Output: Data returned to the requester upon execution of the flow. Its structure is similar to a standard HTTP response. This property is empty when an execution fails.

  • Status: A code that indicates the result of the execution. You can set any value between 200 and 499 using the Return response action.

    • By default, synchronous flows return a 200 OK.

    • Asynchronous flows return a 202 Accepted.

    • If an execution fails, a 500 Internal Server Error code is returned. Flows that fail during execution return a 500 Internal Server Error. 

  • Body: By default, an empty object is returned. 

  • Error: An object returned only if an execution fails due to a non-recoverable error. You can use this object to identify which Flow action failed and the error code returned. This property is empty for successful executions.