Overview
Every workflow execution is logged in the Runs tab. Whether a run succeeded or failed, you can drill into it to see the inputs, outputs, and status of every individual node. This is your primary tool for diagnosing problems and confirming workflows are behaving as expected.Reading the Runs Tab
To access run history:- Open the workflow from the Workflows main page
- Click the Runs tab at the top of the workflow detail page
Reading a Specific Workflow’s Run History
To view run history for a single deployed workflow:- Navigate to that workflow’s production page
- Click the Run History tab at the top of the side editor
Run Statuses
Dry Run Results
Dry run results are separate from saved workflow run history. They are a preview of what would happen for the workflow version and trigger input you selected, without changing CRM data or sending external messages.Inspecting a Failed Run
When a run fails, the run detail view highlights which node caused the failure. Click on that node to expand its details and see:- Inputs - the values that were passed into the node when it executed
- Output - what the node returned (or attempted to return)
- Error message - a description of what went wrong
Debug a Workflow with Ask Reevo
Ask Reevo can read your workflow run history and trigger checks, so you can ask in plain language why a workflow did or didn’t do something instead of opening each run yourself.Explain a run
Ask Reevo can list recent runs for one workflow, a few workflows, or every workflow in your workspace, and can narrow the list by status and start time. It shows the newest runs first: 10 by default, up to 50 at a time. Each run shows its workflow, status, the record it ran on, when it started and finished, and the failure message if it failed. Ask about any one of those runs to get a step-by-step explanation of what it did, why it did or didn’t take a given step, and why it failed if it did. For example:- Show me failed runs across my workflows this week.
- Why didn’t this run send the Slack message?
Find out why a workflow didn’t run for a record
Name the workflow and the record, and Ask Reevo checks how the workflow’s trigger conditions evaluated for that record. It lists every condition with the value it saw and whether the condition passed, names the condition the record failed, and shows what changed on the record when that change was recorded. To start without a record, ask which records the workflow recently skipped, then pick one to debug. For example:- My stage change workflow didn’t run for this opportunity. Why?
- Which contacts did my enrollment workflow skip recently?
- Webhook and schedule triggers have no trigger conditions to check. For a schedule trigger, Ask Reevo tells you whether a run was due since the workflow was last deployed.
- Workflows that aren’t live, such as drafts or workflows with the Active toggle off, are not checked. Ask Reevo tells you the workflow isn’t live.
- A record of a different type than the one the workflow triggers on can never start that workflow, and Ask Reevo says so.
- If the workflow did run for the record, Ask Reevo points you to that run so it can explain what happened.
Common Errors and How to Fix Them
Data Error: 'Invalid record ID format: [value] is not a valid UUID'
Data Error: 'Invalid record ID format: [value] is not a valid UUID'
Integration Error: 'Failed to send Slack message to channel [name]'
Integration Error: 'Failed to send Slack message to channel [name]'
Rule Violation: 'Opportunity stage could not be shifted from [stage] to [stage]: one or more stage criteria weren't met'
Rule Violation: 'Opportunity stage could not be shifted from [stage] to [stage]: one or more stage criteria weren't met'
Data Error: 'output field [name] instruction must reference at least one input variable'
Data Error: 'output field [name] instruction must reference at least one input variable'
Rule Violation: 'AI credits quota exceeded'
Rule Violation: 'AI credits quota exceeded'
System Error: 'Run failed due to a system issue on our end'
System Error: 'Run failed due to a system issue on our end'
Troubleshooting / FAQs
My workflow ran but the record wasn't updated - how do I diagnose this?
My workflow ran but the record wasn't updated - how do I diagnose this?
Why does my dry run say the workflow would not trigger?
Why does my dry run say the workflow would not trigger?
Why is a dry run step marked Not simulated?
Why is a dry run step marked Not simulated?
Why do I see example data in dry run results?
Why do I see example data in dry run results?
An AI Data Transform node ran but some outputs are empty - why?
An AI Data Transform node ran but some outputs are empty - why?
My workflow is Active but it's not triggering - what should I check?
My workflow is Active but it's not triggering - what should I check?
Can I rerun a failed workflow run?
Can I rerun a failed workflow run?
I see a 'System Error' vs. a 'Data Error' - what's the difference?
I see a 'System Error' vs. a 'Data Error' - what's the difference?
My workflow turned off by itself - what happened?
My workflow turned off by itself - what happened?
Still have questions? Sign in and use Ask Reevo for instant answers or to raise a support ticket.