Debug Logs in Guided Workflows
Updated
Debug Logs help you investigate and troubleshoot Guided Workflow execution issues. You can review workflow execution history, inspect execution logs, identify failed nodes, review error details, and generate AI-powered troubleshooting summaries to help diagnose workflow failures.
The Debug Panel provides a centralised view of Guided Workflow executions, making it easier to review execution history and troubleshoot issues without relying on external logging tools.
Currently, the Debug Logs capability is available for the following Nodes and Components:
Screen Nodes
Update Properties
Decision Box
Add API
Custom Field Actions
Secure Screen
Add Notes
The following image captures how logs are displayed on the UI.

Note: To enable this feature in your environment, contact your Success Manager. Alternatively, you can submit a request at tickets@sprinklr.com.
Key Benefits
Rapid Issue Detection – Quickly pinpoint the specific node where the workflow encounters a failure, all without the need to switch between tools.
Swift Resolutions – Access error details and modify the workflow directly from the canvas, enabling faster issue resolution.
Enhanced Testing – Simplify quality assurance and validation by making the debugging process more intuitive and efficient.
Filter Workflow Executions
Use the Debug Panel to search for specific workflow executions.
You can filter executions by:
- Case Number
- Guided Workflow Name
- User Name
- Execution Date Range
You can combine multiple filters to narrow the results and locate a specific workflow execution more quickly.
Filter Debug Logs
Within the Debug Logs view, you can further filter log entries using the following criteria:
- Workflow Status (Success or Failure)
- Node Type
- Execution Time
- Status
These filters help you focus on specific execution events and troubleshoot issues more efficiently.
View Execution Metadata
Debug Logs include execution metadata that helps identify and track workflow runs.
For example, you can view information such as the Guided Workflow Execution ID associated with an execution.
Steps to Access Debug Logs
Whenever you execute a Guided Workflow either from the Guided Workflow Manager or Guided Workflow Canvas, it opens in the quick window.


If the execution fails, an error warning will be displayed in the opened third pane view.
If you want to understand the reason for the execution failure, click the Debug Logs icon on the top bar of the quick window.

The debug logs will open up on the left side of the window. The node with the issue(s) will be highlighted in red for easy identififcation.

To get a detailed view, hover over the respective card and click View Node.

You will be directed to the node where the Guided Workflow is breaking, and that node will get highlighted in blue.

To review detailed information about the error, click View Error.

In the Error Details dialog box, click Troubleshoot to generate an AI-powered analysis of the issue.

The troubleshooting summary is displayed in the same dialog box, providing insights into the likely cause of the error and recommended actions.
Use the recommendations in the summary to update and correct your Guided Workflow configuration.
Review Error Details
The Error Details window provides additional information about execution failures, helping you understand what occurred and where the error was encountered.
You can use this information together with the troubleshooting summary to identify and resolve workflow issues more efficiently.
AI-Powered Troubleshooting
The troubleshooting capability analyses workflow execution logs and provides a summary of the likely cause of a failure.
The analysis can:
- Identify the primary cause of an execution failure.
- Explain the issue in clear, easy-to-understand language.
- Highlight the workflow step or node associated with the issue.
Recommend actions that may help resolve the problem.
Note: AI-generated troubleshooting guidance is intended to assist with diagnosis. Always review the workflow configuration and validate any recommended changes before publishing updates.