Forum Discussion
Automatic refreshes never pull in changes (UPDATED)
We incrementally refresh our semantic model every 30 minutes using the services's scheduler. As far as I know, scheduled refreshes perform a refresh type Automatic. This works fine.That makes little sense as the smallest partition is a daily partition. You will want to look into keeping the "today" partition in direct query mode.
Note: For your API refreshes you should replace "automatic" with "full" to force the refresh.
Hi markmsc,
Thank you for reaching out to the Microsoft Fabric Community Forum. Also, thanks to lbendlin, for his inputs on this thread.
The behaviour you’re seeing is expected with Automatic refreshes. Power BI only reprocesses partitions that aren’t already marked as Ready. If a partition is in the “Ready” state, the service assumes it’s up to date and skips it even if the source data has changed. That’s why scheduled refreshes work later, but on-demand automatic ones appear to do nothing.
Detect data changes: Make sure your incremental refresh policy uses a proper change-tracking column (e.g., ModifiedDate). This tells Power BI which partitions need refreshing. https://learn.microsoft.com/en-gb/power-bi/connect-data/incremental-refresh-overview#detect-data-changes
Query folding: Verify that filters on RangeStart and RangeEnd are folding to the source. If not, incremental logic may skip updates. https://learn.microsoft.com/en-gb/power-bi/connect-data/incremental-refresh-troubleshootPartition states: If partitions stay in “Ready,” Automatic refresh will skip them. You can confirm this via XMLA endpoint or Tabular Editor.
If you need data immediately, you can: Trigger a Full or Data Only refresh via the REST API instead of “Automatic.” Or update the change-tracking column in the source so the partition is re-evaluated. https://learn.microsoft.com/en-gb/rest/api/power-bi/datasets/refresh-datasetHope this clears it up. Let us know if you have any doubts regarding this. We will be happy to help.
Thank you for using the Microsoft Fabric Community Forum.
Hi markmsc,
Thank you for reaching out to the Microsoft Fabric Community Forum. Also, thanks to lbendlin, for his inputs on this thread.
The behaviour you’re seeing is expected with Automatic refreshes. Power BI only reprocesses partitions that aren’t already marked as Ready. If a partition is in the “Ready” state, the service assumes it’s up to date and skips it even if the source data has changed. That’s why scheduled refreshes work later, but on-demand automatic ones appear to do nothing.
Detect data changes: Make sure your incremental refresh policy uses a proper change-tracking column (e.g., ModifiedDate). This tells Power BI which partitions need refreshing. https://learn.microsoft.com/en-gb/power-bi/connect-data/incremental-refresh-overview#detect-data-changes
Query folding: Verify that filters on RangeStart and RangeEnd are folding to the source. If not, incremental logic may skip updates. https://learn.microsoft.com/en-gb/power-bi/connect-data/incremental-refresh-troubleshoot
Partition states: If partitions stay in “Ready,” Automatic refresh will skip them. You can confirm this via XMLA endpoint or Tabular Editor.
If you need data immediately, you can: Trigger a Full or Data Only refresh via the REST API instead of “Automatic.” Or update the change-tracking column in the source so the partition is re-evaluated. https://learn.microsoft.com/en-gb/rest/api/power-bi/datasets/refresh-dataset
Hope this clears it up. Let us know if you have any doubts regarding this. We will be happy to help.
Thank you for using the Microsoft Fabric Community Forum.
Thank you very much for your detailed reply. I think our scenario meets all the detailed prerequisites you mention. As you suggeted, as did another user here, we have changed the API refreshes to Full. Please see my second reply to lbendlin in this topic for more context on that. I marked that person's post as Solution and I wiill do the same here as you also recommended changing the refresh type to Full.