How to Debug Flows

Debugging helps you trace exactly where a user is in a flow, identify steps they are getting stuck on, and confirm that conditions or branches are sending users in the expected direction.

You can access debugging from the bottom-right corner of the editor.

Enrollment

Enrollment is the equivalent of a session in the context of flows.

When a user enters a flow, they are enrolled and move through the steps until they exit. A user can exit by completing the flow, dismissing it, or being disqualified by a condition.

A new enrollment begins each time the flow triggers again for that user.

If a user refreshes the page mid-flow, they return to their current unfinished enrollment instead of restarting from the beginning.

Debugging a Specific User

To debug a specific user's experience, enter their username in the debug panel.

A timeline appears showing every event in their enrollment history with exact timestamps, including:

• when the flow was created
• when the user enrolled
• when each step was executed or consumed

This timeline lets you follow the user's path through the flow step by step.

Event Details

The event sidebar gives you a detailed breakdown of each event.

Clicking on any event shows:

When: the exact date and time the event occurred, plus a relative timestamp, for example 7 minutes ago.

Source: the internal method that triggered the event, such as ConsumeCurrentStepAsync.

Step ID: the unique identifier of the step the event relates to.

Details: a JSON object with additional context, including the consumed step ID and step type.