Workflows now include built-in tools to help you understand what went wrong and find issues faster. Whether you are triaging a list of workflows or debugging a specific failure, these improvements reduce the time spent investigating.
Scout sidebar — Ask questions about a workflow directly from the workflow page. Scout uses your workflow configuration and run history to provide grounded, contextual answers.
Failure-focused list visibility — The workflow list now surfaces failure signals so you can quickly identify which workflows need attention.
Plain-English field readability — Key workflow stage editors now display clearer labels and hints alongside internal field keys, making configurations easier to read and understand.
Scout Sidebar
The Scout sidebar is a read-only assistant that helps you understand and troubleshoot workflows without leaving the page.
Opening Scout
Open any workflow in the admin and look for the Scout button. Click it to open the sidebar. Scout is available on both existing workflows and new workflow pages.
What you can ask
Scout can help with questions like:
"Why did this workflow fail?"
"What does this field do?"
"What happened in the last few runs?"
"Is there a pattern in the recent failures?"
Scout inspects your workflow configuration and recent run history to answer. When multiple failed runs are available, Scout can identify patterns — such as the same step failing repeatedly or a recent regression.
Note: Scout is read-only in this release. It cannot edit your workflow, apply fixes, or execute any actions. Use Scout's recommendations to guide your own changes in the workflow editor.
Each workflow has its own conversation history. Switching between workflows starts a fresh context so answers stay relevant.
Failure-Focused List Visibility
The workflow list now includes failure-oriented signals to help you prioritize investigation.
What you'll see:
The workflow list surfaces information about recent failures so you can identify problem workflows at a glance — without opening each one individually.
What to do:
Start your investigation from the list. Identify workflows with recent failures, then open the workflow and use Scout or the run history to dig deeper.
Plain-English Field Readability
Key workflow stage editors now display clearer labels alongside the internal field keys you may already be familiar with.
High-usage editor surfaces show plain-English descriptions for fields and variables. Internal keys are still visible and accessible — nothing has been removed or renamed. This is an additive improvement to help you read configurations faster.
What to do:
Use the plain-English labels to quickly understand what a field does. When you need the exact key for troubleshooting or advanced configuration, the original key is still shown.
Frequently Asked Questions
Can Scout fix workflow issues automatically?
No. Scout is read-only in this release. It provides explanations and recommendations, but you apply any changes yourself in the workflow editor.
Do I need to enable this for my organization?
No. These improvements are available automatically in the admin workflow pages for all organizations.
Does this change existing workflow configurations or templates?
No. All existing keys, paths, and field behavior remain unchanged. Plain-English labels are shown alongside existing keys, not as replacements.
What should I try first when investigating a workflow issue?
Start with the failure signals in the workflow list to find which workflows are failing. Then open the workflow and use the Scout sidebar for context-grounded diagnosis. If you need more detail, check the run history and debugger.