Skip to main content

Workflow Trace Response

Custom GUI and Python agent runs can return a workflow trace. In raw API responses this is workflowTrace; in the Python SDK it is response.workflow_trace.

Choosing A Trace

Use response.action_trace to inspect individual /Operator browser actions, such as navigation, typing, clicks, and element selection. Use response.workflow_trace to inspect the execution of an Agent Studio custom workflow: its workflow-level status, GUI steps, and nested workflows. A workflow step that invokes Operator can include its own nested action trace. The workflow envelope and timed GUI step timestamps use startTs and endTs.
endTs is omitted while a workflow or step is still running. It is also absent when no end time was recorded.

Workflow Envelope

Trace Nodes

GUI Nodes

GUI workflow step nodes have kind: "gui_step" and include stepId, stepType, status, and children. They include startTs and, once complete, endTs. Nested workflow nodes have kind: "sub_workflow", carry their own workflow trace, and follow the same timestamp fields.

Python Nodes

Python workflow traces can include the following child nodes: