Automated Read the Docs Build Failure Alerts
Every hour, WebRun opens Read the Docs, checks every project for a failed documentation build, saves the full build log to a Google Drive folder for whoever fixes it, and posts an alert to Slack naming the project and version so broken docs don't sit live and confusing for readers.
How do I get alerted when a Read the Docs build fails?
WebRun checks Read the Docs every hour for a failed documentation build across every project. It saves the full build log to Google Drive for whoever fixes it, and posts a Slack alert naming the project and version, so broken docs get fixed instead of quietly leaving readers with an outdated or confusing page.
- Broken doc builds get an alert within the hour they fail
- Build logs are saved automatically for faster fixes
- Readers are far less likely to land on outdated or broken docs
Built for technical writers · developer relations teams · open source maintainers · platform 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
readthedocs.org/accounts/loginin a real browser with your saved login - no setup, no API keys. -
1
Read the Docs - check for failed documentation builds
- Open Read the Docs and check the latest build for each project
- Capture the project, version, and error for anything that failed
- Skip builds already alerted on
Done when Every newly failed documentation build is listed with its project and error.
-
2
Google Drive - save the build log
drive.google.com
WebRun opens Google Drive to save the build log. - Save the full build log for each newly failed build to the docs folder
- Name the file with the project and version
- Keep a running folder so failure history is easy to review
Done when Every newly failed build has its log saved to Drive.
-
3
Slack - alert the team
slack.com
WebRun opens Slack to alert the team. - Post an alert to the docs channel naming the project, version, and error
- Link the saved build log
- Skip projects already alerted on this hour
Done when The docs channel has an alert for every newly failed documentation build.
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 the build or fix the docs?
No. WebRun only reports the failure and saves the log. Fixing the documentation source is always done by a person.
Does a failed build take the old docs offline?
No, and that's exactly the risk. The old version often stays live and readers don't realize the latest build is broken, which is why the alert matters.
How fast does a failure get reported?
Within the hour it happens, since every project's latest build is checked each hour.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.