Catch failed Airflow DAGs on Astronomer fast
Every hour, WebRun opens Astronomer, checks DAG runs across your deployments for failures, messages the on-call engineer on WhatsApp with the failed DAG and a link to the logs, and schedules a fix window on Google Calendar for recurring failures.
- No credit card
- Under $0.01 per run
- Cancel anytime
How do I get alerted when an Airflow DAG fails on Astronomer?
WebRun checks Astronomer DAG runs every hour across your deployments. The moment one fails, it messages the on-call engineer on WhatsApp with the DAG, the task, and a link to the logs, and schedules a fix window on Google Calendar if the same DAG has failed more than once that week, so recurring breakage gets real time booked against it.
- Failed DAGs reach the on-call engineer within the hour
- Recurring failures get a scheduled fix window, not repeated pages
- Every alert links straight to the run logs, no manual searching
Built for data engineering teams · platform engineers · analytics engineers · DevOps 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
cloud.astronomer.ioin a real browser with your saved login - no setup, no API keys. -
1
Astronomer - check DAG run status
WebRun opens Astronomer to check DAG run status. - Open Astronomer and list DAG runs from the last hour across deployments
- Check each run's status and task failures
- Flag any DAG that failed or is stuck retrying
Done when Every DAG run from the last hour has a checked status.
- 2
- 3
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 retry or fix the DAG on its own?
No. WebRun only reports the failure and schedules time to fix it. Retrying a task or editing the DAG is left to a human.
Why message on WhatsApp instead of just logging it?
A failed DAG is often time-sensitive, feeding a downstream report or model. A direct WhatsApp message gets it in front of the on-call engineer faster than a dashboard they'd have to check.
What counts as a recurring failure?
The same DAG failing more than once in the same week triggers a scheduled fix window, so a one-off blip doesn't clutter the owner's calendar.
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.