Browse the Knowledge Center
Workflows
Test and debug a workflow
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.
Read the article: Monitoring workflow runs and versions