Automated Prefect Flow Failure Alerts
Every hour, WebRun opens Prefect Cloud, checks every flow run since the last check, saves the log output for any failed run to Google Drive, and posts the failure with its flow name and error straight to Slack.
How do I get alerted when a Prefect flow run fails?
WebRun checks Prefect Cloud every hour for failed flow runs, saves the full log output to Google Drive, and posts the failure with its flow name and error straight to Slack. Data engineering teams find out about a broken pipeline within the hour, with the logs already saved for whoever picks up the fix.
- A failed flow run reaches Slack within the hour
- Logs are already saved before anyone starts debugging
- Only failures post, so the channel stays signal not noise
Built for data engineering teams · platform engineers · analytics engineering teams
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
app.prefect.cloudin a real browser with your saved login - no setup, no API keys. -
1
Prefect - check for failed flow runs
- Open Prefect Cloud and check runs since the last pass
- Filter to any run in a failed or crashed state
- Note the flow name, the failed task, and the error message
Done when Every failed run since the last check has been captured with its error.
-
2
Google Drive - save the failure logs
drive.google.com
WebRun opens Google Drive to save the failure logs. - Open the pipeline logs folder in Google Drive
- Save the failed run's log output as a dated file
- Name the file with the flow and run id for quick lookup
Done when The failure's full log output is saved and easy to find.
-
3
Slack - post the failure to Slack
slack.com
WebRun opens Slack to post the failure to Slack. - Open the data engineering channel in Slack
- Post the flow name, the failed task, and the error message
- Link to the saved log file in Google Drive
Done when The team has the failure and its log link in Slack.
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
Does WebRun retry the failed flow?
No. It only reads run status and saves logs. Retrying, resuming, or editing a flow stays a decision for the engineer on call.
Will successful runs also post to Slack?
No. Only failed or crashed runs generate an alert, so the channel stays useful instead of noisy with routine successes.
How long are the saved logs kept?
As long as they stay in the Google Drive folder. Every failure gets its own dated file, so nothing overwrites a prior incident.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.