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
Introduction:
I am new to the Fabric Community and have three years of experience with Power BI. I have passed the PL-300 exam and have a good understanding of the Power BI Pro license.
Fabric Subscription:
Currently using the F4 Fabric license.
Challenge:
We recently migrated a workspace to Fabric and are facing some challenges. We are importing Salesforce tables into Dataflow Gen2, and from there, copying them into a Lakehouse.
Dataflow Gen2 to Lakehouse
Dataflow Gen2 to Warehouse
Any suggestions?
Solved! Go to Solution.
Hello! The rate limit isn't based solely on the size of the data. The F4 sku has limits on the number of concurrent Spark jobs and API calls that can be made, so that may have soemthing to do with your issue. When the limits are exceeded you could get errors indicating the limit has been reached. F4 enforces concurrency limits and queue sizes so only a certain number of jobs can run at the same time. You can hit rate limits because of frequent API calls (frequent calls in a short amount of time could cause the rate limit to be reached regardless of data size), concurrent jobs, complex operations and burst usage. You can open look into spreading the calls out over a longer period of time or upgrading to a higher SKU. Also, here is a link where you can open a support ticket if needed: Microsoft Fabric Support and Status | Microsoft Fabric
Proud to be a Super User! | |
Hello! The rate limit isn't based solely on the size of the data. The F4 sku has limits on the number of concurrent Spark jobs and API calls that can be made, so that may have soemthing to do with your issue. When the limits are exceeded you could get errors indicating the limit has been reached. F4 enforces concurrency limits and queue sizes so only a certain number of jobs can run at the same time. You can hit rate limits because of frequent API calls (frequent calls in a short amount of time could cause the rate limit to be reached regardless of data size), concurrent jobs, complex operations and burst usage. You can open look into spreading the calls out over a longer period of time or upgrading to a higher SKU. Also, here is a link where you can open a support ticket if needed: Microsoft Fabric Support and Status | Microsoft Fabric
Proud to be a Super User! | |
The Power BI Data Visualization World Championships is back! Get ahead of the game and start preparing now!
Check out the November 2025 Power BI update to learn about new features.
| User | Count |
|---|---|
| 59 | |
| 46 | |
| 42 | |
| 23 | |
| 17 |
| User | Count |
|---|---|
| 190 | |
| 122 | |
| 96 | |
| 66 | |
| 47 |