Catch a failed report refresh before anyone sees stale numbers
Every morning, WebRun opens Power BI, walks your workspaces to see which datasets refreshed cleanly overnight and which failed or ran late, logs every failure in an Airtable incident table with its error text, and drafts an email to each report owner in Gmail that you approve before it goes out.
- No credit card
- Under $0.01 per run
- Cancel anytime
How do I get alerted when a Power BI dataset refresh fails?
WebRun checks your Power BI workspaces every morning to see which datasets failed, skipped, or ran late overnight. It logs each failure in Airtable with the error text, repeat count, and affected reports, then drafts an email to each report owner in Gmail for you to approve, so stale dashboards get caught before breakfast.
- Stale dashboards are caught before the morning stand-up
- Repeat offenders surface with a running failure count
- Owners get a clear, human-approved email instead of a raw error
Built for data teams · BI analysts · analytics engineers · IT operations
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.powerbi.comin a real browser with your saved login - no setup, no API keys. -
1
Power BI - check overnight refreshes
powerbi.microsoft.com
WebRun opens Power BI to check overnight refreshes. - Open Power BI and go through each workspace you monitor
- Read the refresh history on every scheduled dataset
- Capture any refresh that failed, was skipped, or finished later than usual
- Record the dataset, workspace, last successful refresh time, and the error message shown
- Note which reports depend on each failed dataset
- Read only. Never trigger a refresh, edit a dataset, or change a schedule
Done when Every failed or late refresh from overnight is captured with its error and affected reports.
-
2
Airtable - log every failure
airtable.com How to Automate Airtable
WebRun opens Airtable to log every failure. - Open your data incident table in Airtable
- Add a row per failed dataset with the workspace, error, and time of failure
- Increment a repeat count when the same dataset failed on a previous day
- Set the status to open and assign the owner listed for that workspace
- Sort the view so datasets failing repeatedly sit at the top
Done when Airtable holds an open incident row for every failure, with repeats counted.
-
3
Gmail - draft the owner email
gmail.com How to Automate Gmail
WebRun opens Gmail to draft the owner email. - Draft one email per report owner in Gmail listing their failed datasets
- State the dataset, the error, the last time the data was good, and which reports are affected
- Leave every email in the drafts folder for you to read and send. Nothing sends on its own
- Skip owners already emailed about the same failure in the last 24 hours
Done when A draft email is waiting in Gmail for every affected report owner.
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 email report owners without me?
No. Every message is left as a draft in Gmail for you to read and send. WebRun never sends mail on its own, so a false alarm never reaches a stakeholder.
Does it re-run the failed refresh?
No. WebRun reads refresh history only. It never triggers a refresh, edits a dataset, changes a gateway, or alters a schedule, so it cannot make a data problem worse.
How do I spot a dataset that keeps breaking?
Airtable counts repeats. When the same dataset fails again, WebRun increments the repeat count on the existing incident row and sorts it to the top, so chronic failures are obvious.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.