Data Monitoring / Power BI Refresh & Data Reliability
Power BI: Refresh schedule collisions
Several semantic models contend for the gateway at the same minute. Overlay refresh start and finish times with gateway load and shared source demand.
Environment and inputs: Power BI Desktop and Power BI service; gateway, connector, capacity and license capabilities depend on the deployed configuration.
Failure scenario
Several semantic models contend for the gateway at the same minute. Confirm the cause before choosing a fix.
Evidence to collect
Overlay refresh start and finish times with gateway load and shared source demand. Record the time, affected scope and a healthy comparison interval.
Fix the confirmed cause
Stagger independent schedules and verify that the business freshness deadline still holds. Write the expected result first. Change one relevant setting at a time.
Check the result and hand over
Repeat the check for refresh schedule collisions 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.