Data Monitoring / Power BI Refresh & Data Reliability
Power BI: Refresh duration baselines
A refresh that used to finish quickly now approaches its schedule interval. Compare like-for-like run durations with row volumes, gateway resource use and upstream latency.
Environment and inputs: Power BI Desktop and Power BI service; gateway, connector, capacity and license capabilities depend on the deployed configuration.
Failure scenario
A refresh that used to finish quickly now approaches its schedule interval. Confirm the cause before choosing a fix.
Evidence to collect
Compare like-for-like run durations with row volumes, gateway resource use and upstream latency. Record the time, affected scope and a healthy comparison interval.
Fix the confirmed cause
Separate volume growth from per-row slowdown before changing capacity or refresh frequency. Write the expected result first. Change one relevant setting at a time.
Check the result and hand over
Repeat the check for refresh duration baselines using the same scope and a representative interval. Check that the symptom is resolved, expected records are present and downstream results are correct. If coverage, correctness or latency worsens, restore the recorded configuration through the agreed rollback process.
Scope and precautions
Prefer read-only access and limit queries to the relevant period or dataset. This example has not been tested on your systems. Test changes in an approved environment. Keep credentials and sensitive data out of shared evidence.