Overview
You can now navigate directly between a workflow's version history and execution history. This feature connects two critical debugging flows: understanding what you built (versions) and how it performed (executions).
In this article, we'll be covering how to view executions for a specific version, how to view the workflow definition for a specific execution, and how to restore a previous version.
Understanding Versions and Executions
Versions are snapshots of your workflow's logic at specific points in time. Each time you save changes in the Builder, you create a new version.
Executions are individual runs of your workflow. Every time your workflow triggers, it creates an execution using the currently published version.
The connection between them works bidirectionally. From a version, you can see how that code performed in production. From an execution, you can see what code was running when that execution occurred.
Viewing Execution History for a Specific Version
Use this when you want to see how a particular version performed in production.
- Navigate to
Workflows > [Your Workflow] > Version History - Locate the version you want to investigate
- Click the three-dot menu next to the version
- Select View execution history
The execution history page opens with an automatic filter showing only executions from that version.
Alternative path: If you're viewing version details, you can also click View execution history from the Details tab within that version.
This matters because isolating executions by version shows you the direct impact of specific changes. When you compare execution counts between versions, you can see whether your updates improved or degraded performance.
Viewing Workflow Definition for a Specific Execution
Use this when you're investigating a failure or unexpected behavior and need to see exactly what code was running.
- Navigate to
Workflows > [Your Workflow] > Execution History - Find the execution you want to investigate
- Click on the execution to open its details
- On the Workflow Details tab, click the three-dot menu
- Select View workflow definition
The version that ran for that execution opens. The header shows the version number (e.g., "Version 35"). If this differs from your current published version, you know changes have been made since this execution ran.
This step connects the failure to specific code. You can now compare this version to your current published version to identify what changed.
Restoring a Previous Version
Use this when you've identified a version that worked better than the current one.
- Navigate to the version you want to restore (via Version History or from an execution)
- Review the workflow definition to confirm this is the correct version
- Open the JSON view within that version (the JSON icon is inside the graph view)
- Select all JSON content and copy it (Cmd+A, Cmd+C on Mac; Ctrl+A, Ctrl+C on Windows)
- Navigate to the Builder tab
- Open JSON view (inside the graph)
- Select all existing JSON and delete it
- Paste the copied JSON (Cmd+V on Mac; Ctrl+V on Windows)
- Click Save or Publish
This creates a new version with the restored logic. Publishing as a new version maintains your version history—you're not deleting the versions in between.
Troubleshooting
I can't find the execution I'm looking for
After viewing executions for a specific version, the version filter persists until you clear it. Look for the filter indicator in Execution History and click the X to remove it.
Also verify you're in the correct workflow by checking the workflow name at the top of the page.
The version looks the same as the current version
Visual graphs may look identical while node inputs, output mappers, or error handling changed. Click into individual nodes to inspect their configuration.
Use JSON view to see all changes, not just visual differences. This reveals modifications to node settings that don't appear in the graph.
After pasting JSON to restore a version, I get an error
The JSON may not have been fully selected. Try again using Cmd+A or Ctrl+A to select all content before copying.
If you edited the JSON manually, validate your syntax. The error message will often indicate what's wrong.
If the error persists and the JSON wasn't modified, contact support—there may be a compatibility issue between the old version and current system constraints.
I restored an old version but the workflow still fails
The failure may not be caused by workflow logic. Verify that APIs, data sources, and other external systems are functioning.
Review the execution history for the version you restored. It may have had failures too—just fewer than the current version.
Compare error messages between old failures and new ones. Different errors suggest the environment or inputs have changed since that version last worked.
Related Articles
- Version History - Track all changes to your workflows over time