Automated Sisense Stale Dashboard Alerts
Every morning, WebRun opens Sisense, checks every dashboard and data model's last successful refresh time, opens a Trello card for any one that has gone stale past its expected schedule, and posts the full list to Microsoft Teams.
How do I catch stale Sisense dashboards before stakeholders do?
WebRun checks every Sisense dashboard and data model's last refresh time each morning, opens a Trello card for anything overdue with its owner named, and posts the full stale list to Microsoft Teams. Analytics teams catch a stale dashboard before a stakeholder opens it and spots numbers that stopped updating days ago.
- A stale dashboard gets caught before a stakeholder notices
- 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 BI teams · analytics engineers · data ops 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
sisense.comin a real browser with your saved login - no setup, no API keys. -
1
Sisense - check refresh status
- Open Sisense and list every dashboard and its data model
- Check each model's last successful refresh time
- Flag any model past its expected refresh schedule
Done when Every model's refresh status is checked against its schedule.
-
2
Trello - open a chase card
trello.com
WebRun opens Trello to open a chase card. - Open the data ops 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 team channel in Microsoft Teams
- Post the full stale dashboard list with owners
- Put the most overdue models at the top
Done when The team has today's stale dashboard 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 refresh itself?
No. It only reads the last refresh time in Sisense and flags what's overdue. Running the refresh stays a decision for the model's owner.
How is a model marked stale?
By comparing its last successful refresh against its expected schedule. Only models genuinely past due get a chase card.
Will a dashboard's viewers see a warning?
No. Nothing changes on the dashboard 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.