Monitoring workflow runs and versions

Once a workflow is active, Vetta runs it every time its trigger fires, and keeps a record of each run and each version. You get two levels of visibility: Global Analytics, a workspace-wide overview across all workflows, and the Runs and Versions tabs of each workflow. Together they tell you whether your automations are healthy, why a run failed, and exactly which version did what.

The workflows overview

On the Workflows page, click Global Analytics to see automation health across the workspace (and View All Workflows to go back to the list):

• Run health: total runs, failed runs and the fail rate over the period
• Needs attention: any workflow with a failed run among its recent runs, with its last failure and top cause
• Failures by cause: failed runs classified by error type
• Runs & outcomes: recent runs and their results
• Token consumers: which workflows use the most AI tokens (relevant when you use the AI CRM Agent step)

Use this page as a daily health check before you dig into an individual workflow.

Workflow runs

Each run is one execution of a workflow. A run moves through these statuses:

• Not started: created but not yet picked up
• Enqueued: waiting to run
• Running: in progress
• Completed: finished
• Failed: stopped with an error

Open a workflow's Runs tab to see how it's doing: how many runs completed, failed or are in progress, and the average run time. Filter the list by status or by date and time, and open any run to see which steps it went through and which version it used.

Execution logs

Each run has a step-by-step log. Click any step in a run to inspect:

• The trigger event details
• Which steps ran, and their status
• The input each step received
• The output each step produced (available to later steps as variables)
• The error, if the step failed

In the editor, variables read null because nothing has run yet. In a run, every variable shows the real value that run used, which is how you check that a step got the data you expected.

Testing and debugging

A workflow has no test button: you check it on real runs. The one exception is the HTTP Request step. Its Test tab lists every variable the request uses: type a test value for each and click Send Request. The request goes out from your browser and the response comes back with its status and time. Nothing is saved as a run.

Once the workflow is live, Runs is where you debug:

1. Filter the list to Failed and open a run. The step that broke has a red cross.
2. Click it. Its output shows the error, for example a 503 from another app.
3. Fix the cause, then click Re-run.

Re-run has three options:

• Retry from failed step: keeps the steps that already worked and runs the rest again (only for failed runs)
• Restart from beginning: runs every step again
• Re-run on latest version: runs it on the workflow's newest version instead of the one the run originally used

Turn on Create a new run to keep the original run untouched in the history, which is useful for auditing what failed. Leave it off and the same run is reset and re-executed in place, which keeps the runs list tidy.

Narrated video · 1:09

2 linked topics

Debugging a workflow. There is no test button, so you check real runs. The exception is the HTTP request, whose Test tab lists its variables, takes test values and sends the request from your browser, showing status and time without saving a run. Once live, filter Runs to Failed, open the run, click the step with the red cross to read its output error, fix the cause and click Re-run. Retry from failed step keeps what already worked.

Transcript

A workflow has no test button: you check it on real runs. The one exception is the HTTP request. Its Test tab lists every variable the request uses. Type a test value for each, and click Send Request. The request goes out from your browser, and the response comes back with its status and time. Nothing is saved as a run. Once the workflow is live, Runs is where you debug. Filter to Failed, and open a run: the step that broke has a red cross. Click it, and its output shows the error, here a 503 from the billing tool. When the cause is fixed, click Re-run. Retry from failed step keeps the steps that already worked and runs the rest again. Back on All, the new run has completed. Every morning, Alex asks Claude how last night's runs went. Claude finds four failed runs, all at one step. Claude, ChatGPT or any assistant you connect to Vetta works on your real workspace, so ask daily, then give it a bigger job each week. In Vetta, open Runs, filter to Failed, then click Re-run.

Workflow versions

Vetta keeps every version of a workflow, so you can always see what ran when. A workflow version is in one of these statuses:

• Draft: being edited; never runs
• Active: the version that runs when the trigger fires
• Deactivated: turned off with Deactivate; kept in history
• Archived: an older version replaced by a newer one

When you change a live workflow, for example by adding a step, the live version stays untouched. Your change starts a new draft, version 2, and version 1 keeps running until you activate the new one. Then version 1 is archived, and the Versions tab keeps the whole history. A run that had already started when you activated version 2 finishes on version 1; only new runs use version 2.

With version history you can:

• Review previous versions and see how the automation evolved
• See which version each run used when you debug
• Open an earlier version and choose Use as draft (confirm with Override Draft) to roll back a bad change
• Discard Draft to abandon unpublished edits and keep the active version as it is

Narrated video · 1:11

2 linked topics

Making a workflow live and keeping track of it. Activate appears once the workflow has a trigger and at least one step; confirming puts version one live. Editing then starts a new draft, version two, while version one keeps running until you activate the new one, which archives the old. Versions keeps the history. Runs shows completed, failed, in progress and average run time, and each run shows its steps. Re-run can retry from the failed step, restart, or use the latest version. Deactivate stops it.

Transcript

Nothing runs until you activate it. Once a workflow has a trigger and at least one step, Activate appears. Click it and confirm, and version one goes live. Now change something, like adding a step, and the live version stays untouched. It starts a new draft, version two, and version one keeps running until you activate the new one. Then version one is archived, and Versions keeps the whole history, so you can always see what ran when. Open Runs to check how it's doing: completed, failed, in progress, and the average run time. Filter the list, and open any run to see which steps it went through. Re-run can retry from the failed step, restart from the beginning, or run it again on the latest version. And Deactivate stops it whenever you need to. Each release, Alex asks Claude to activate and keep a baseline. Claude reads 112 runs, then activates version three. Claude, ChatGPT or any assistant you connect to Vetta works on your real workspace, so make it routine, then give it a bigger job each week. In Vetta, check Versions, then open Runs next week.

Notifications

When a workflow reaches a Form step, the person who has to fill it in gets a Form Input Needed notification saying the form is waiting for their input. See Notifications in Vetta.

For failures, make Global Analytics part of your routine: the Needs attention panel lists every workflow as soon as one of its recent runs fails.

Common questions

Key outcome

You can now see at a glance whether your automations are healthy, find the exact step and input behind any failure, re-run it once the cause is fixed, and roll back to an earlier version if a change went wrong, all while the active version keeps running untouched.