Re-running a Workflow Execution

Last updated: August 27, 2026

Re-running a Workflow Execution

Category: Workflows & Automation

Re-running an execution from the Workflow Runs view now tests your fix, not the original problem. Previously, a re-run replayed the exact workflow version and CRM snapshot the original run used — so if you fixed a broken field mapping and republished, re-running a failed execution just failed the same way all over again. Now, every re-run uses your workflow's current published version and re-fetches the CRM record's live data.

How It Works

  • A re-run always targets the ramp's current published workflow version, and re-fetches the trigger record from your CRM at the moment you re-run it — not the data that was captured when it first ran.

  • Every re-run creates a new, independent execution row, regardless of the original's outcome. The original run's history is preserved untouched, so you always have a record of what happened the first time.

  • If the run-detail dialog shows your workflow's current published version is different from the version the run you're looking at actually used, a version-drift note appears — so you know before confirming that the re-run will follow different rules than the original.

How to Re-run an Execution

  1. Go to Workflow Runs and find the execution you want to re-run.

  2. Open the run and select Re-run.

  3. If a version-drift note appears, review it — it tells you the re-run will use a newer published version than the one the original run used.

  4. Confirm. A new execution row is created using the current workflow and live CRM data; the original row is left exactly as it was.

A Few Things to Keep in Mind

Re-running a failed or otherwise non-success execution keeps the same underlying record identity, and OnRamp checks whether a successful execution already exists for that trigger on that workflow before proceeding — so you can't accidentally create two projects for the same record by re-running a failed run more than once.

Re-running an already-successful execution is still allowed, and deliberately creates a second project — useful if you genuinely want a second project for the same record. This one isn't blocked by the duplicate check above.

If the CRM record no longer exists, the re-run fails with a clear message rather than silently proceeding on stale data.

Frequently Asked Questions

If I fix a broken field mapping, will re-running an old failed execution now succeed?
Yes — that's the point of this change. The re-run uses your current published workflow, so a fix you've since made and published will apply.

Will re-running overwrite the original run's history?
No. The original execution row is left untouched; the re-run always creates a new, separate row.

What if the CRM record was updated since the original run?
The re-run reads the record's current live values, not what was captured the first time — so it reflects any changes made in your CRM since.

Can re-running create a duplicate project?
Re-running a non-success execution is blocked if a successful execution already exists for that same trigger on that workflow. Re-running an already-successful execution is allowed and will create a second project on purpose.