Forum Discussion
AleSota
10 months agoFrequent Visitor
Scheduled refresh completes successfully but dataset doesn’t update (gateway)
Hi everyone, I’m having an issue where my report’s scheduled refresh shows as “Completed,” but the data doesn’t actually update. The only way I can get the data to refresh is by manually going t...
tayloramy
Super User
10 months agoHi AleSota,
This “Completed but nothing changes” pattern usually means the service did run a refresh, but the model is either (a) being overwritten by something else after the refresh, (b) reading from the wrong place via the gateway mapping, or (c) constrained by incremental refresh/filters so no new rows qualify. Below is a quick checklist I’d run, then a deeper dive with why each matters.
Quick solution
- Rule out OneDrive/SharePoint auto-sync overwriting the model.
Open your semantic model settings and turn OneDrive refresh off if this PBIX is connected to OneDrive/SharePoint. Otherwise the service can pull the older PBIX every hour and silently overwrite post-refresh changes. See: Automatic vs manual OneDrive refresh. - Verify the gateway mapping points to the exact same Blob container/account as Desktop.
In the dataset’s Gateway connection mapping, make sure every data source path and credential matches what you use locally (no “DEV” container in the gateway while Desktop points to “PROD”). See: Configure scheduled refresh and Gateway troubleshooting. - If you use Incremental Refresh, force a one-time full refresh and re-check your policy.
Common issues are date type mismatches and filter logic that exclude “new” rows, so the refresh runs but finds nothing to load. See: Incremental refresh troubleshooting. - Add a “RefreshStamp” measure/table to prove the model is actually changing.
Create a small table with DateTime.LocalNow() (or a measure like UtcNow = NOW()) and display it in a visual. If the stamp changes on scheduled refresh history entries, the model is refreshing; if not, something else (like OneDrive sync) is overwriting. - Prefer VNet Data Gateway for Azure sources behind firewalls.
Since your source is Azure Blob Storage and you’re blocked by firewall policy, a VNet Data Gateway is the supported pattern. It avoids oddities of a Standard gateway for cloud sources behind private endpoints. See: VNet data gateway for Power BI and the general gateway docs here.
If you share a screenshot of your Gateway mapping and the OneDrive refresh setting from the model, I can help pinpoint which of these is biting you.
If you found this helpful, consider giving some Kudos. If I answered your question or solved your problem, mark this post as the solution.