Power BI is turning 10, and we’re marking the occasion with a special community challenge. Use your creativity to tell a story, uncover trends, or highlight something unexpected.
Get startedJoin us for an expert-led overview of the tools and concepts you'll need to become a Certified Power BI Data Analyst and pass exam PL-300. Register now.
We have Dataflows that utilize API Sources that we would like to incrementally refresh. These are working as expected since the source filters the data to the latest snapshot data which has a Data Through Date that allows us to detect the period we want to refresh. We are using incremental to support reporting on current and prior period data.
The issue we are seeing is that each time the incremental refresh runs, Power BI makes multiple calls to the source API. While this doesn't present a problem for most of our sources, we have a couple that provide larger result sets and are memory intensive. Making multiple calls to the source (5-8x within 30 seconds of the refresh starting) uses too much memory and ultimately brings down that API.
When we run full refreshes, the Power BI Service only calls the source once.
A couple of things to note:
Any idea why the Source API would be called so many times in rapid succession?
When you say Incremental Refresh are you referring to the Power BI version (including RangeStart and RangeEnd datetime filters for the data source, and Power BI's partition management), or something that you have created manually in your query?
This is your chance to engage directly with the engineering team behind Fabric and Power BI. Share your experiences and shape the future.
Check out the June 2025 Power BI update to learn about new features.
User | Count |
---|---|
43 | |
19 | |
18 | |
15 | |
14 |
User | Count |
---|---|
32 | |
19 | |
19 | |
16 | |
16 |