Catch a dataset that stopped refreshing before anyone acts on it
Every morning, WebRun opens Domo, reads the last update time on every dataset that feeds a dashboard, compares it against the refresh cadence you expect, raises a Trello card for anything stale, and warns the analytics owner on WhatsApp before a meeting is run on old numbers.
- No credit card
- Under $0.01 per run
- Cancel anytime
How do I find out when a dataset has stopped refreshing?
Every morning WebRun opens Domo, reads the last update time on every dataset that feeds a dashboard, and compares it against the refresh schedule you expect. It raises a Trello card for anything stale and warns the analytics owner on WhatsApp, so no meeting is run on yesterday's numbers.
- A broken feed is caught before the dashboard is read out in a meeting
- Every stale dataset arrives with its connector and its downstream cards named
- Cards close themselves once the data refreshes again
Built for analytics teams · data engineers · BI owners · operations leaders
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
domo.comin a real browser with your saved login - no setup, no API keys. -
1
Domo - read last refresh on every dataset
domo.com
WebRun opens Domo to read last refresh on every dataset. - Open Domo and list the datasets that feed your reported dashboards
- Read the last successful update time and the expected refresh cadence for each one
- Flag any dataset whose last update is older than its cadence allows
- Note the connector or dataflow behind each stale dataset, and which cards depend on it
Done when Every reported dataset is confirmed current or recorded as stale with its age.
-
2
Trello - raise a card for stale feeds
trello.com How to Automate Trello
WebRun opens Trello to raise a card for stale feeds. - Raise one card per stale dataset on your data team board
- Put the dataset name, hours since the last update, the connector or dataflow, and the cards affected on it
- Close cards automatically on a later run once the dataset refreshes again
- Keep a count of how often each dataset goes stale so a fragile connector is obvious
Done when Every stale dataset has an open card naming its cause and its downstream cards.
-
3
WhatsApp - warn the analytics owner
whatsapp.com How to Automate WhatsApp
WebRun opens WhatsApp to warn the analytics owner. - Message the analytics owner the stale datasets and which dashboards read from them
- Lead with anything feeding a dashboard used in a standing meeting today
- Stay silent on mornings when every dataset is current. WebRun never reruns a dataflow or edits a dataset
Done when The analytics owner knows which dashboards are showing old numbers.
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 rerun a dataflow or fix the connector?
No. WebRun reads refresh times and reports what is stale. Rerunning a dataflow, reauthorizing a connector, or editing a dataset stays with your data team.
How does it know a dataset is stale?
It compares the last successful update against the refresh cadence you expect for that dataset, so a daily feed is flagged after a day and an hourly feed much sooner.
Will it flood me with cards every morning?
No. Cards close on their own once a dataset refreshes again, and mornings when everything is current pass without a WhatsApp message at all.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.