Data Monitoring / Power BI Refresh & Data Reliability
Power BI: Time-zone freshness errors
A freshness card appears several hours behind although ingestion is timely. Compare source timestamps, service refresh timestamps and report display conversions against UTC.
Environment and inputs: Power BI Desktop and Power BI service; gateway, connector, capacity and license capabilities depend on the deployed configuration.
Failure scenario
A freshness card appears several hours behind although ingestion is timely. Confirm the cause before choosing a fix.
Evidence to collect
Compare source timestamps, service refresh timestamps and report display conversions against UTC. Record the time, affected scope and a healthy comparison interval.
Fix the confirmed cause
Normalize stored monitoring timestamps and label the display time zone explicitly. Write the expected result first. Change one relevant setting at a time.
Check the result and hand over
Repeat the check for time-zone freshness errors 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.