Automated Bugsnag Regression Alerts
Every hour, WebRun opens Bugsnag, filters errors to the ones previously marked fixed, finds any that have new events in a later app version, works out which release they came back in, posts the detail to Microsoft Teams, and pings the on call developer on Telegram.
How do I get alerted when a bug I fixed comes back?
WebRun checks Bugsnag every hour for errors previously marked fixed that have started recording events again. It identifies the app version and release the error returned in, posts the detail with a link to Microsoft Teams, and pings the on call developer on Telegram within the hour.
- A bad fix is caught within the hour, not at the next release review
- Every alert names the release the crash returned in
- Single stray events stay quiet under your event threshold
Built for mobile developers · on call engineers · 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 - find fixed errors happening again
bugsnag.com
WebRun opens Bugsnag to find fixed errors happening again. - Open Bugsnag and filter errors to those with a fixed status
- Find any with new events recorded since the last run
- Note the app version and release the error reappeared in, and the event count since it returned
- Ignore errors already reopened and reported in an earlier run
Done when Every regression since the last run is listed with its release.
-
2
Microsoft Teams - post the regression detail
microsoft.com
WebRun opens Microsoft Teams to post the regression detail. - Post each regression with the error name, the release it returned in, and the event count
- Add the link to the error in Bugsnag so the stack trace is one click away
- Show when it was originally marked fixed so the gap is obvious
Done when Every regression from this run is posted in Microsoft Teams.
-
3
Telegram - ping the developer on call
telegram.org
WebRun opens Telegram to ping the developer on call. - Send a one line ping naming the error and the release it came back in
- Only ping for regressions above the event count you set, so a single stray event stays quiet
- Leave reopening the issue and shipping a fix to the developer
Done when The on call developer has been pinged about every real regression.
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 reopen or change the error in Bugsnag?
No. WebRun reads the error list and reports what it found. Reopening an error, assigning it, or rolling back a release stays with your developers.
How is this different from a new error alert?
It watches only errors you already marked fixed. A new error alert tells you about something never seen before, while this catches a bad fix that let an old crash back into a later release.
Will a single stray event wake someone up?
No. The Telegram ping only fires above the event count you set, so one straggler stays quiet and a genuine return of an old crash gets the on call developer within the hour.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.