Monitor every workflow run
Every execution leaves a trail — status, timestamps, credits, and payloads. WEXTL run history lives in the builder’s Runs sidebar so debugging never leaves the canvas.
- GDPR
- Data Encryption
- 2FA
- Local Data Region
Runs sidebar listing recent workflow executions with status badges
What Run history helps you do
From trigger to evidence
- 1
A run starts
Webhook, schedule, or Run once kicks off the flow.
- 2
Steps record results
Each node keeps the data you need to understand the path.
- 3
Scan status, time, and credits
Debugging that stays beside the canvas. The Runs tab lists executions for this workflow — filter, search, and open a run without leaving the builder.
Succeeded, failed, and needs-attention runs sit in one list with relative time and credit chips.
When compliance asks what fired last week, you open the run — not a spreadsheet export.
Runs list filters including needs-attention and status chips
Search when the list is long
Full-text search (on plans that include it) finds a run by payload content, not only by id.
Click a hit to open the matched node with the term highlighted in the results panel.
Runs sidebar full-text search for James Joe with matching run hits highlighted