IO Debug Console

The IO Debug Console helps developers monitor Identity Orchestration workflow execution in real time while previewing a workflow. When debug mode is enabled, node-level success and error details are streamed back to the browser so you can understand the execution path and troubleshoot issues faster.

Enable Debug Mode

Debug logs are available only when both of the following are enabled:

In the workflow configuration, set Debug Mode to true when creating a new workflow or editing an existing one.
In workflow preview, enable Debug Mode so the preview URL includes debugMode=true.

If only one of these settings is enabled, the IO Debug Console will not display logs.

How It Works

When debug mode is enabled:

After each workflow stage executes, the stage output is stored in the workflowSession.
The corresponding workflow document is also updated with the latest execution details.
The webpage reads the streamed debug data from the workflowSession and displays it in the IO Debug Console.

This gives developers a step-by-step view of workflow execution, making it easier to identify failures, unexpected branches, and script behavior.

Debug URL Example

https://{appName}.devhub.lrinternal.com/workflow?workflowName={workflowName}&client_id={oidc_client_id}&debugMode=true

Note: Debug logs are shown only when the workflow configuration has debug mode enabled and the preview URL contains debugMode=true.

Debug Console Log Structure

Each log entry in the IO Debug Console currently includes the following fields:

Field	Description
Node	The workflow node currently being executed.
Log	A high-level execution message returned by the core backend.
Description	A detailed backend message that explains the internal flow and execution path.

For Script nodes, the Description field may contain more detailed execution context. This is especially helpful for understanding custom logic and troubleshooting script behavior.

Example Console Output

The following example shows what a successful sendemail node log could look like in the IO Debug Console:

Node	Log	Description
`Send Email`	Successfully executed operation	The operation was completed successfully.

A failed node log might look like this:

Node	Log	Description
`User Exists`	User exist operation failed	Failed to verify if the user exists.

These examples help show how the Log* field gives you the high-level result, while Description provides the extra context needed for troubleshooting.

Common Use Cases

Trace workflow execution in real time during testing.
Verify whether a node completed successfully or followed an error path.
Troubleshoot Script node behavior using the detailed description field.
Confirm whether the expected data is being passed between workflow stages.