Forum Discussion
Advocate IIDatafow Gen2: inconsistent behavior/fails and CU consumption
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:
Memorable MemberThank you for stating what everyone faced with 104100 errors and other DFg2 shenanigans should be hollering from the rooftops. I sure am. But get this: support just got back to me yesterday and told me that the workaround to handle error 104100 (when ingesting from an on-prem DB) is by design (according to the internal team, whoever they are)! Meanwhile, if you try to do your ingest using only one DFg2, you will be blocked by a 104100 error! How is that by design and not a bug fro crying out loud!?
Advocate IIElement115 thanks for the feedback - thats certainly interesting to hear!
however in my particular case, as explained in my initial post, there is nothing involved thats on prem! everything is located in fabric.
and even if the flow does not fail, I still find the quite extreme fluctuations in CU consumption astonishing considering that it should always consume the same amount if neither the flow nor the data changed...