Scheduled refresh completes successfully but dataset doesn’t update (gateway)

[AleSota]

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 to the Open Data Model section of my semantic model and clicking Refresh,  or locally in Power BI Desktop and republishing.

Here’s the setup:

• The report is connected to a Blob Storage through a Standard Gateway, since our firewall restrictions prevent a direct connection.

• After publishing the report, I configured the gateway credentials and set up a scheduled refresh.

• Everything appears fine, no errors in the service, and the refresh history shows successful runs, yet the dataset doesn’t refresh in reality.

Has anyone run into this before or know why the refresh reports success but doesn’t actually update the data? I really need the scheduled refresh to work automatically.

Thanks in advance for your help!

[GilbertQ]

Hi @AleSota 

Once the refresh is completed, could you click on the Reset to default button just in case there are any filters which might be causing your data to appear that it is not changing?

[AleSota]

I'd have loved for the problem to be this, but it isn't  

[R1k91]

as @GilbertQ said probably it's just a matter of refreshing data on the report not in the model.

I've seen this happening many times.

Me: hello!

Customer: hello, my report is out of date again, please help!

Me: ok, can you click that green arrow on top right, please?

Customer: oh, that button you always tell me to click before entering panic-mode?

Me: yes, that one.

Customer: ok, now it's working! Thank you

Me: great, bye.

[tayloramy]

Hi @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

1. 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.
2. 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.
3. 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.
4. 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.
5. 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.

[AleSota]

Thanks @tayloramy . I've checked all of these, and I only need to try the vnet option. 

Maybe that would help. For the rest, everything seems in order

[tayloramy]

Hi @AleSota, 

Can you send us a screenshot of the refresh history screen of the report? 

Can you also open the semantic model in the service and use the Explore option and verify that data is not updated? This will let you see directly what is in the model to troubleshoot more. I suspect the model itself does have new data and the issue is downstream of that, as I've never seen the service successfully refresh but not actually refresh. 

If you found this helpful, consider giving some Kudos. If I answered your question or solved your problem, mark this post as the solution. 

[AleSota]

Thanks @tayloramy . I've checked all of these, and I only need to try the vnet option. 

Maybe that would help. For the rest, everything seems in order

[AleSota]

@v-sshirivolu Thanks. If any of these setting were wrong, the semantic model wouldn't refresh at all, correct? But it is refreshing when I access the editing section of the data modelm in Power BI Service. 

[v-sshirivolu]

Hi @AleSota ,
Since your semantic model refresh completes successfully when triggered manually but the scheduled refresh shows as Completed without updating data, the issue is likely specific to the scheduled refresh process rather than credentials or the gateway. One common cause is that some queries, particularly those connected to Blob Storage, might have Include in report refresh turned off in Power Query Editor. This allows a manual refresh to update the data but skips those queries during a scheduled refresh. Another possibility is that incremental refresh settings are not aligned with your data’s update frequency, which could prevent new data from being included in scheduled refreshes. It’s also worth checking that the gateway mapping for your data source is correct and reapplying credentials if needed. Occasionally, caching or metadata issues in Power BI can cause a refresh to report success without pulling new data, so forcing a full refresh or making a minor model change can help reset this. Since manual refresh works, starting with these checks is usually the fastest way to resolve the issue, and if the problem persists, reviewing gateway logs or opening a support ticket with Microsoft using your refresh history can help uncover any service side factors.

[v-sshirivolu]

Hi @AleSota ,

I hope the information provided above assists you in resolving the issue. If you have any additional questions or concerns, please do not hesitate to contact us. We are here to support you and will be happy to help with any further assistance you may need.

[v-sshirivolu]

Hi @AleSota ,

I hope the above details help you fix the issue. If you still have any questions or need more help, feel free to reach out. We’re always here to support you.

[v-sshirivolu]

Hi @AleSota ,
Thanks for reaching to Community Forum.

Thank you for providing details about your setup. I understand that your scheduled refresh completes without errors, but the report data is not updating. Since you are using a Standard Gateway to connect to Blob Storage behind a firewall, there are several factors to consider. Please verify that the credentials configured in the gateway for Blob Storage access are accurate and valid, as expired or insufficient permissions can result in a successful refresh that does not update the data. Ensure that your dataset in Power BI Service is correctly linked to the appropriate data sources via the gateway. Incorrect or incomplete data source mapping can prevent proper data refresh. Power BI caching could also be a factor, as it may retain outdated data or metadata after a refresh; clearing the cache by making a minor change to the dataset or performing a full refresh can help resolve this. At last confirm that your gateway is up to date and functioning correctly, as some issues may not appear in the refresh logs but could be identified in the gateway’s logs. Reviewing your queries in Power Query Editor, especially if you use parameters or incremental refresh, can also ensure fresh data is pulled consistently. 
Regards,
Sreeteja.