Skip to main content

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 main page
  2. Click the Runs tab at the top of the workflow detail page
You’ll see a list of all past runs: 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: 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

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.
Open Ask Reevo from the workflow’s page. Ask Reevo uses the workflow you have open, and the run you have selected in Run history (opened from the Run history tab, or the View run history switch on some workflow layouts), so you can ask “why did this run fail?” without naming either one.

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?
If a run is too large to explain in full, Ask Reevo tells you so. Open the run in the run detail view to review its steps directly.

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?
Skip history is short-lived. Reevo keeps up to the 200 most recent skips for each workflow and clears them after a day with no new skips, so ask soon after the change you expected to trigger the workflow.
A few situations get a different answer:
  • 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

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 AI Data Transform output has an instruction with no input variable in it, so there is nothing for the node to transform.Fix: Edit that output’s instruction and insert the input value it derives from using the variable picker, then re-deploy.
An AI-powered node could not call the model because your workspace ran out of AI credits mid-run.Fix: Review AI credit usage in your workspace settings, or contact your Reevo admin about raising the quota. Runs resume normally once credits are available.
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.
The node fills in the outputs it can and leaves the rest empty, either because the input did not contain that value or because the AI could not produce a value the field would accept. It does not guess or fill in a placeholder, and the workflow keeps running with the outputs that did come through. Open the node in the run detail view and compare its outputs against its inputs, then tighten the instruction or point the output at a CRM field so the AI can see that field’s valid options.
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). To see which condition stopped a specific record, use Ask Reevo to find out why the workflow didn’t run for that record or which records it recently skipped. See Debug a Workflow with Ask Reevo.
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 and use Ask Reevo for instant answers or to raise a support ticket.