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
Click any row to open the run detail view and inspect each individual node.
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
Click any row to open the run detail view and inspect each individual node.
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.
Dry run also reports Projected side effects and Would modify records. Projected side effects show messages, webhooks, or notifications the workflow would have sent. Would modify records shows the number of CRM records the workflow would create, update, or delete.
AI-powered steps run with a real model during dry runs, so those steps can consume credits even though CRM writes and external messages are blocked.
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
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'
A Record Action node received an invalid value for the record ID field.Fix: Go back into your workflow and correct the record ID reference in the affected node, then re-deploy.
Integration Error: 'Failed to send Slack message to channel [name]'
Integration Error: 'Failed to send Slack message to channel [name]'
The Slack API failed or your Slack integration has an issue.Fix: Verify that your Slack integration is still connected and working under Settings → Integrations. If the issue persists, contact Reevo support to investigate further.
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'
A Move Stage node tried to advance an opportunity to the next stage, but required stage criteria on the current stage haven’t been fulfilled.Fix: Either fulfill the stage criteria and re-trigger the workflow, or add a condition to ensure the workflow only runs when the criteria are already met.
System Error: 'Run failed due to a system issue on our end'
System Error: 'Run failed due to a system issue on our end'
An unexpected system-level problem occurred on Reevo’s end.Fix: Contact Reevo support with the workflow name and the run timestamp so the issue can be investigated.
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?
Open the run in the Runs tab and expand the Update Records node. Check its inputs to see what values it was trying to write. If the inputs look correct but the record still wasn’t updated, confirm the node was targeting the right record - the trigger record vs. a found record - and that the record ID resolved correctly.
Why does my dry run say the workflow would not trigger?
Why does my dry run say the workflow would not trigger?
The selected record or event did not match the workflow’s trigger conditions. Open the dry run’s trigger condition details to see which condition did not match, then adjust the selected input or update the trigger filters.
Why is a dry run step marked Not simulated?
Why is a dry run step marked Not simulated?
Some steps depend on live external systems, approval decisions, async workflow dispatch, scheduling, scoring, or Ask Reevo behavior that cannot be reproduced safely offline. Reevo skips those steps during dry run, marks them Not simulated, and continues where possible without sending, writing, charging, or dispatching anything for that step.
Why do I see example data in dry run results?
Why do I see example data in dry run results?
Enrichment and research steps use representative example data during dry runs instead of calling external providers. This lets downstream steps preview how they would read that output without performing the live provider request.
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?
Four things to verify: (1) the workflow has been Deployed (not just saved), (2) the Active toggle is on, (3) the trigger’s filter conditions are being met by the events occurring, and (4) the triggering event is actually occurring in Reevo (e.g., confirm the record was actually updated, not just viewed).
Can I rerun a failed workflow run?
Can I rerun a failed workflow run?
Rerunning a specific failed run is not currently supported. To re-execute the workflow for a record, trigger the event again (e.g., update the record field to re-fire a Record Updated trigger).
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?
Data Error means the workflow hit a known, user-resolvable issue - the error message will tell you exactly what to fix. System Error indicates an unexpected problem on Reevo’s end. If you consistently see System Errors on a workflow, contact Reevo support with the workflow name and run timestamp.
My workflow turned off by itself - what happened?
My workflow turned off by itself - what happened?
Reevo automatically deactivates workflows that error too frequently or create a cyclical trigger loop, to prevent your credits from being wasted. Common causes include: a workflow running repeatedly with data errors, or a Record Updated trigger with loose conditions that then updates the same record and re-triggers itself. Review your trigger conditions and error history, fix the underlying issue, and reactivate the workflow.
Still have questions? Sign in and use Ask Reevo for instant answers or to raise a support ticket.