Objective
This article shows you how to open a single Studio execution and trace it step by step, which widgets ran, in what order, which events fired, and where the flow went next, so you can work out exactly what a caller or texter experienced.
Product
Studio
Environment
Twilio Console
User Account Permission/Role(s) Required
This page requires the Studio executions read permission on the account.
Procedure
- In the Twilio Console, select Orchestration in the left sidebar.
- Select Studio, then Flows.
- Select the flow, then select the Logs tab.
- Select the execution's identifier in the Contact column.
- Review the Properties section, which lists Execution SID, Contact SID, Flow SID, Triggered by, Trigger SID, Engine, Revision, and Execution status.
- On the Steps tab, review the table of steps with Date, Widget name, Widget class, Event, Source flow, and Transitioned to. The first row is the Trigger step.
- Select a widget name to open its step details in a side panel. Expand Debugging information to see any related debugger events, and open the Widget and Flow Properties tab to see the widget's properties and the flow variables at that point.
- Close the side panel to return to the table.
- Select the Flow data tab to see the execution's full context.
Additional Information
- Source flow tells you whether the step ran in this flow, shown as Parent flow, or inside another flow called as a subflow, shown as Subflow. The link opens whichever flow the step actually ran in.
- Engine shows whether the execution ran on the New Studio Engine or the Classic Studio Engine. Hover the value for an explanation and a Learn more about Studio's New Engine link. Twilio is migrating all accounts to the New Studio Engine.
- If a step has no debugger events, Debugging information shows No records found.
- If the execution is still Active, a Stop execution action appears at the top of the page.
This content was generated by AI and reviewed, edited, and verified by a human.