Automated AppVeyor Stale Build Chase List
Every morning, WebRun opens AppVeyor, reviews build history across your projects, finds any project whose most recent builds have failed for more than two days straight, logs it to Airtable with the failing step, and posts a follow-up note in Notion for the owning developer.
How do I stop AppVeyor builds from staying broken for days?
WebRun reviews AppVeyor build history every morning, finds any project whose builds have failed for more than two days straight, and logs it to Airtable with the failing step and owner. It then posts a Notion follow-up note per stale build, so a red build does not quietly sit there for a week without anyone circling back.
- No build stays red for more than a day without a tracked follow-up
- Owners get named automatically instead of someone asking around
- Fixed builds drop off the list the next morning on their own
Built for .NET development teams · Windows software teams · release engineers · 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
ci.appveyor.com/loginin a real browser with your saved login - no setup, no API keys. -
1
AppVeyor - check for stale failures
- Open AppVeyor and review build history for each project
- Identify any project whose last build succeeded more than two days ago
- Note the failing step and the project owner for each
Done when Every project failing for more than two days is identified with its failing step.
-
2
Airtable - log the stale build
airtable.com
WebRun opens Airtable to log the stale build. - Open the Stale Builds base
- Add or update a row per project with the failing step, days red, and owner
- Mark any project fixed since the last check as resolved
Done when The Airtable base reflects every currently stale failing build.
-
3
Notion - post the follow-up note
notion.so
WebRun opens Notion to post the follow-up note. - Open the engineering follow-ups Notion page
- Post a note per stale build naming the project, days red, and owner
- Ask the owner to update status or reassign it
Done when A follow-up note exists in Notion for every build that has been red more than two days.
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 WebRun rerun the build or fix the code?
No. It only tracks how long a build has been failing and who owns it. Fixing the code and rerunning the build stays with the developer.
How long does a build need to be red before it shows up?
More than two days of consecutive failures. That threshold can be adjusted if your team wants a shorter or longer grace period.
What happens once a build is fixed?
The next morning's check sees the passing build and marks the Airtable row resolved, so it drops off the active follow-up list automatically.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.