Automated AtScale Stale Model Alerts
Every morning, WebRun opens AtScale, checks every semantic model's last successful build against its expected schedule, opens a Trello card for any model that has gone stale, and posts the full list to Microsoft Teams.
How do I catch AtScale semantic models that stopped rebuilding?
WebRun checks every AtScale semantic model's last successful build each morning, opens a Trello card for anything stale with its owner named, and posts the full list to Microsoft Teams. Data platform teams catch a model that stopped rebuilding before a BI tool downstream quietly serves outdated numbers to business users.
- A stale semantic model is caught before BI tools serve old numbers
- Every overdue model has a named owner and a tracked card
- The team sees the full stale list in one Teams post each morning
Built for data platform teams · analytics engineers · BI 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
atscale.comin a real browser with your saved login - no setup, no API keys. -
1
AtScale - check model build status
- Open AtScale and list every published semantic model
- Check each model's last successful build time
- Flag any model past its expected build schedule
Done when Every model's build status is checked against schedule.
-
2
Trello - open a chase card
trello.com
WebRun opens Trello to open a chase card. - Open the data platform board in Trello
- Create a card for each stale model naming its owner and how overdue it is
- Add it to this week's chase list
Done when Every stale model has a tracked card with an owner.
-
3
Microsoft Teams - post the stale list
microsoft.com
WebRun opens Microsoft Teams to post the stale list. - Open the data platform channel in Microsoft Teams
- Post the full stale model list with owners
- Put the most overdue models at the top
Done when The team has today's stale model list in Teams.
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
Does WebRun trigger the model rebuild itself?
No. It only reads the last build time in AtScale and flags what's overdue. Triggering a rebuild stays the model owner's decision.
How is a model marked stale?
By comparing its last successful build against its expected schedule. Only models genuinely past due get a chase card.
Will BI users see a warning on the model?
No. Nothing changes on the model itself. The chase list is internal, in Trello and Teams, for the owner to act on.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.