Automated Bugsnag Release Stability Scorecard
Every Monday, WebRun opens Bugsnag, compiles the past week's new error events and stability score for each active release, logs the numbers as a new row in Google Sheets so the trend builds over time, and updates a Notion release health page so anyone can see which release is having trouble at a glance.
How do I track release stability across my Bugsnag error data?
WebRun compiles your Bugsnag error counts and stability score by release every Monday. It logs the numbers to a Google Sheets tracker so trends build over time, and updates a Notion release health page, so a release having trouble stands out immediately instead of getting lost in a stream of individual error reports.
- Struggling releases stand out the Monday after they ship
- Stability trends are tracked automatically week over week
- The release health page stays current without manual updates
Built for mobile engineering teams · release managers · QA teams · engineering managers
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.bugsnag.com/user/loginin a real browser with your saved login - no setup, no API keys. -
1
Bugsnag - compile the week's error and stability data
bugsnag.com
WebRun opens Bugsnag to compile the week's error and stability data. - Open Bugsnag and pull the past week's error events by release
- Record each release's stability score
- Note which release had the sharpest increase in new errors
Done when Every active release has this week's error count and stability score.
-
2
Notion - log the numbers to a sheet
notion.so
WebRun opens Notion to log the numbers to a sheet. - Log this week's error counts and stability scores as a new row per release
- Flag the release with the sharpest increase in new errors
- Keep prior weeks in place so the trend is visible
Done when This week's numbers are logged as a new row for every active release.
-
3
Google Sheets - update the release health page
google.com
WebRun opens Google Sheets to update the release health page. - Update the release health page with the current stability score per release
- Highlight the release flagged for a sharp error increase
- Keep the page as the current at a glance summary
Done when The Notion page reflects this week's stability score for every active release.
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 fix or dismiss any errors?
No. WebRun only reads error counts and stability scores. Triaging or fixing an error is always done by an engineer in Bugsnag.
How is the stability score calculated?
It's the stability score Bugsnag itself calculates for each release. WebRun reports the number, it does not calculate its own.
Can I compare releases over time?
Yes. Every week's numbers are added as a new row in the same sheet, so you can see how each release trended after it shipped.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.