Automated Alteryx Failure Triage
Every morning, WebRun signs in to Alteryx, collects the scheduled workflows that errored or were cancelled overnight, captures the workflow, the schedule, the error message, and the owner, opens or updates a triage row in Airtable, and posts the owned failure list to your data team's Notion page.
How do I triage overnight data workflow failures?
WebRun signs in to Alteryx every morning and collects the scheduled workflows that errored, were cancelled, or ran abnormally long overnight. It opens or updates one triage row per workflow in Airtable with the error and the owner, then publishes the owned failure list to your team's Notion page.
- Every overnight failure has an owner and a row by 7am
- Repeat failures surface with their consecutive-day count instead of duplicating
- Slow runs are flagged before they turn into tomorrow's outage
Built for data teams · analytics engineers · BI managers · operations analysts
What does WebRun do on every run?
The exact actions WebRun takes, in order - in plain language, so you can adjust anything.
-
WebRun signs in and gets to work
Opens
alteryx.comin a real browser with your saved login - no setup, no API keys. -
1
Alteryx - collect overnight failures
alteryx.com
WebRun opens Alteryx to collect overnight failures. - Sign in to Alteryx and open the scheduled workflow run history
- Filter to runs since the last check that errored, were cancelled, or ran far longer than usual
- Capture the workflow name, the schedule, the start time, the duration, and the error message
- Note the workflow owner recorded against each one
Done when Every failed or abnormal run since the last check is captured with its error.
-
2
Airtable - open a triage row per failure
airtable.com
WebRun opens Airtable to open a triage row per failure. - Open your Data Pipeline Triage base in Airtable
- Check whether the workflow already has an open triage row, and if so add today's failure as a repeat
- Create a new row for first-time failures with the workflow, the error, the owner, and the run time
- Set status to Needs triage and leave resolution notes to the human owner
Done when Every failing workflow has exactly one open triage row in Airtable.
-
3
Notion - publish the owned failure list
notion.so
WebRun opens Notion to publish the owned failure list. - Post this morning's failure list to your data team's Notion page
- Put repeat failures at the top with the number of consecutive days they have failed
- Show the owner next to each workflow so triage has a name attached
- Note how many failures from yesterday are now resolved
Done when The data team has today's owned failure list in Notion.
How is each run configured?
Secure by default
Connect once, stays signed in
WebRun signs in once and keeps each session in a persistent environment, so every run picks up right where it left off.
Every action is checked against this policy before it runs.
Questions, answered
Will it rerun a failed workflow?
No. WebRun reads the run history and files the triage row. It never reruns, edits, enables, or disables a workflow. Rerunning stays a human decision after someone reads the error.
Does a workflow that fails three nights create three rows?
No. WebRun updates the existing open triage row and increases its consecutive-failure count, so a chronically broken workflow reads as one loud row rather than a pile of duplicates.
Does it catch runs that succeeded but took far too long?
Yes. Runs that took much longer than their own recent average are included and marked as slow, because a workflow crawling to the finish often breaks the next night.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.