> ## Documentation Index
> Fetch the complete documentation index at: https://help.reevo.ai/llms.txt
> Use this file to discover all available pages before exploring further.
# Workflow Troubleshooting & Run History
> The Runs tab gives you a complete history of every time your workflow executed - what succeeded, what failed, and exactly what happened at each step. This guide explains how to read run history and resolve common errors.
## 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:
1. Open the workflow from the [Workflows](https://app.reevo.ai/workflows) main page
2. Click the **Runs** tab at the top of the workflow detail page
You'll see a list of all past runs:
| Column | What It Shows |
| :-------------- | :-------------------------------- |
| **Date / Time** | When the workflow run started |
| **Status** | The overall outcome of the run |
| **Trigger** | What event initiated this run |
| **Duration** | How long the run took to complete |
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:
1. Navigate to that workflow's production page
2. Click the **Run History** tab at the top of the side editor
You'll see a list of all past runs for that workflow. Hover over any row for additional detail:
| Field | What It Shows |
| :----------------- | :---------------------------------------------------------------- |
| **Trigger Record** | Which record triggered the workflow |
| **Updated Record** | Which records were updated during the run |
| **Run Time** | How long the run took |
| **Credits** | How many credits were consumed |
| **Triggered** | When the run began |
| **Completed** | When the run finished |
| **Error** | Which node failed and an error message explaining what went wrong |
Click any row to open the **run detail view** and inspect each individual node.
***
## Run Statuses
| Status | What It Means |
| :---------- | :------------------------------------------------------------------------------------- |
| **Success** | The workflow completed all nodes without errors |
| **Fail** | A known, user-resolvable error occurred (e.g., a contact was missing an email address) |
| **Error** | An unexpected system-level error occurred |
| **Running** | The workflow is currently executing |
***
## 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 result | What It Means |
| :--------------------------------------- | :---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Dry run complete: no issues** | The simulated path completed successfully. |
| **Dry run completed with errors** | At least one simulated step failed, but the result still includes the path and step details that were available. |
| **Dry run failed** | The simulated run failed. Open the step details to see the error. |
| **Dry run paused** | The workflow reached a step that would pause or wait during a live run. |
| **Dry run blocked by validation errors** | The workflow still has Deploy Checklist issues that must be fixed before Reevo can simulate it. |
| **Not simulated** | A step's real behavior cannot be reproduced offline, so Reevo skips it and continues the simulation where possible. Nothing is sent, written, charged, or dispatched for that step. |
| **Example data** | An enrichment or research step returned representative sample output instead of calling its external provider. |
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
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.
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.
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.
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
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.
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.
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.
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.
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).
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).
**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.
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](https://reevo.ai/) and use Ask Reevo for instant answers or to raise a support ticket.