Forum Discussion
Datafow Gen2: inconsistent behavior/fails and CU consumption
- 2 years ago
Hi chris__1 , Joshrodgers123
This particular failure (calling /workspaces and receiving 429) is happening due to an internal throttling issue that has been resolved since beginning of this week.
Please monitor these refreshes for a bit and see if you continue to observe failures due to "429" error. If so, let me know and sharing the session\request\dataflow ID from the refresh history screen:
thank you Joshrodgers123 - its good to know that I am not alone seeing this behavior.
As our trial is running out soon I think its going to be difficult have to convince the right people to put this product into production and to spend money on it. Not being able to understand why a workload fails is one thing - but to even have to pay for it as your CU go up... thats not good.
Hi chris__1
Thanks for using Fabric Community. Apologies for the issue you have been facing.
For handling such scenarios we would need more information regarding your workspace details, session id etc. Our engineering team would better understand the issue and help you. Hence I request you to create a support ticket here:
Microsoft Fabric Support and Status | Microsoft Fabric
Please provide the ticket number here so that I can closely follow up and provide you with a solution.
Thanks.