Join us at FabCon Atlanta from March 16 - 20, 2026, for the ultimate Fabric, Power BI, AI and SQL community-led event. Save $200 with code FABCOMM.
Register now!The Power BI Data Visualization World Championships is back! Get ahead of the game and start preparing now! Learn more
Hi! All,
I'm getting 429 errors on my Dataflow. It occurs like once a week or sometimes twice but DF refreshes after a manual refresh is triggered.
Thanks for your help.
Solved! Go to Solution.
Hii @PowerZBI
A 429 error in Power BI Dataflows indicates throttling (too many requests or resource contention). This can happen during scheduled refreshes when multiple dataflows or datasets refresh at the same time, or when the source system enforces rate limits. Since the refresh succeeds when run manually, it’s likely a temporary capacity or source-side limit. To reduce this, stagger refresh schedules, avoid overlapping refreshes, reduce dataflow complexity/API calls, and check if the source has request limits. If the issue persists, it’s recommended to monitor capacity usage or raise a Microsoft support ticket.
Hi! @PowerZBI
This could be due to the throttling issue. Try changing it to different time or maybe different sharepoint site. You can also refer to old solutions if that helps.
If you have a Pro license you can open a Pro ticket at https://admin.powerplatform.microsoft.com/newsupportticket/powerbi
I discussed with our COE lead and she mentioned the same. Thank you for your reply, @AnkitKukreja I'll check other links as well. Thank you to you @rohit1991 too.
Hi! @PowerZBI
This could be due to the throttling issue. Try changing it to different time or maybe different sharepoint site. You can also refer to old solutions if that helps.
If you have a Pro license you can open a Pro ticket at https://admin.powerplatform.microsoft.com/newsupportticket/powerbi
Hii @PowerZBI
A 429 error in Power BI Dataflows indicates throttling (too many requests or resource contention). This can happen during scheduled refreshes when multiple dataflows or datasets refresh at the same time, or when the source system enforces rate limits. Since the refresh succeeds when run manually, it’s likely a temporary capacity or source-side limit. To reduce this, stagger refresh schedules, avoid overlapping refreshes, reduce dataflow complexity/API calls, and check if the source has request limits. If the issue persists, it’s recommended to monitor capacity usage or raise a Microsoft support ticket.
The Power BI Data Visualization World Championships is back! Get ahead of the game and start preparing now!
| User | Count |
|---|---|
| 48 | |
| 46 | |
| 44 | |
| 16 | |
| 15 |