Debug Console
Before You Start: Two Conditions Required
Debug logs only appear when both of these are enabled. Enabling just one will show nothing.
How It Works
When both conditions are met and a user progresses through a workflow preview:
- After each stage executes, the stage output is stored in the
workflowSession. - The workflow document is updated with the latest execution details.
- The page reads the streamed data from the
workflowSessionand renders it in the Debug Console panel.
This gives you a step-by-step breakdown of every node: what ran, what the outcome was, and what path the flow took.
Debug Preview URL
https://{appName}.devhub.lrinternal.com/workflow?workflowName={workflowName}&client_id={oidc_client_id}&debugMode=true
Reading the Console: Log Fields
Each entry in the Debug Console corresponds to one node execution:
| Field | What it tells you |
|---|---|
| Node | The workflow node that just executed |
| Log | High-level outcome message from the backend |
| Description | Detailed internal execution context: especially useful for Script nodes |
Script node troubleshooting
For Script nodes, the Description field contains the most detail. If a custom script behaves unexpectedly, start here: it often surfaces the exact error or unexpected data condition.
Example Output
What to Use It For
- Trace which nodes executed and in what order during a test run.
- Confirm whether a node took the
trueorfalseoutput path. - Inspect Script node behavior using the Description field.
- Verify that expected data is being passed between workflow stages before going to production.