This time we’re going bigger than ever. Fabric, Power BI, SQL, AI and more. We're covering it all. You won't want to miss it.
Learn moreGet Fabric Certified for FREE during AI Skills Fest. This week only. Secure your voucher 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?
Don't miss out on Data Days, June 15 through August 7. Learn Fabric, Power BI, SQL, AI and more.
Check out the May 2026 Power BI update to learn about new features.
| User | Count |
|---|---|
| 16 | |
| 11 | |
| 10 | |
| 8 | |
| 7 |
| User | Count |
|---|---|
| 41 | |
| 36 | |
| 36 | |
| 28 | |
| 20 |