Data Monitoring / Power BI Refresh & Data Reliability
Power BI: Gateway cluster node differences
A refresh succeeds on one gateway node but fails on another. Compare connector versions, required drivers and network access across cluster members.
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 succeeds on one gateway node but fails on another. Confirm the cause before choosing a fix.
Evidence to collect
Compare connector versions, required drivers and network access across cluster members. Record the time, affected scope and a healthy comparison interval.
Fix the confirmed cause
Align the supported configuration and verify failover with a representative source connection. Write the expected result first. Change one relevant setting at a time.
Check the result and hand over
Repeat the check for gateway cluster node differences 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.