Forum Discussion
Understanding Gen1 Dataflow Refresh
- 1 year ago
Hi vamshikrishna20 ,
Power BI incremental refresh will only re-process partitions where data has changed, or those that failed in a previous run. When you cancel a refresh after it’s already loaded some partitions, Power BI doesn’t roll everything back it will pick up from the last successful partition next time, only reloading the ones that need it.
So after a cancelled refresh, your next refresh is typically incremental and much faster, which is why you only saw the latest partitions in the logs. This is normal behavior Power BI is designed to save time and resources by not reloading data it already ingested.
If you ever need a true full refresh (reload all partitions from scratch), you’d have to change the incremental refresh policy or delete and re-create the dataflow. But for most cases, letting Power BI handle it this way is fine.
For more insight, check the refresh history and the CSV logs to see exactly which partitions loaded and how many rows were written.
vamshikrishna20, Can you please respond to super user probing question to further progress on your ask?
Thanks,
prashanth