Power BI Refresh Failure and Data Freshness Audit
Look at refresh history and find causes and patterns.
The Open buttons send the prompt text as currently shown below to that site only when you click. Fill in the placeholders first.
[VERIFY] is an editorial flag, not a blank to fill. Wherever the prompt shows [VERIFY], check that item against a reliable source before you use it.
Audit refresh reliability. Refresh history for the last 30 days (date, duration, result, error message): [REFRESH_HISTORY]. Schedule and sources: [SCHEDULE_AND_SOURCES]. Who was told about failures: [ALERTING]. Present a table of dates, results and durations, then summarise the pattern in three sentences. Compute the success rate (successful refreshes divided by attempts), average and median duration, the longest, and the trend in duration (a lengthening refresh often warns of a timeout), and the failures per cause such as credentials, source maintenance, size growth or timeouts [VERIFY], with arithmetic and the sample size. Check how many hours data was stale during each failure. Look for patterns by day and time, and avoid blaming people. Return the table, an alerting plan with owners, the first three checks and fix owner for each failure type, a short first-response runbook, and a freshness banner design showing the last successful refresh time. Refresh limits depend on the licence and capacity [VERIFY].
Fill in before use
Optional: type your details and the prompt above updates. Nothing is saved or sent.
Replace each bracketed placeholder with your own details, then paste into Any AI or another assistant.