Data Monitoring / Power BI Refresh & Data Reliability
Power BI: Incremental refresh boundary gaps
Records near a partition boundary disappear from refreshed results. Inspect RangeStart and RangeEnd predicates with exact boundary timestamps and the model's partition policy.
Environment and inputs: Power BI Desktop and Power BI service; gateway, connector, capacity and license capabilities depend on the deployed configuration.
Failure scenario
Records near a partition boundary disappear from refreshed results. Confirm the cause before choosing a fix.
Evidence to collect
Inspect RangeStart and RangeEnd predicates with exact boundary timestamps and the model's partition policy. Record the time, affected scope and a healthy comparison interval.
Fix the confirmed cause
Use a nonoverlapping boundary convention and test records exactly at both ends of the interval. Write the expected result first. Change one relevant setting at a time.
Check the result and hand over
Repeat the check for incremental refresh boundary gaps 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.