Forum Discussion

chris__1's avatar
chris__1
Icon for Advocate II rankAdvocate II
2 years ago
Solved

Datafow Gen2: inconsistent behavior/fails and CU consumption

I am having some trouble understanding why a Dataflow Gen2 is failing sometimes.   As you can see from the screenshot of the refresh history the dataflow is working fine for some time (running ever...
Dataflows
General Comment
General Question
Need Help
  • pqian_MSFT's avatar
    pqian_MSFT
    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:

     

     

chris__1's avatar
chris__1
Icon for Advocate II rankAdvocate II
2 years ago

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.

Element115's avatar
Element115
Icon for Memorable Member rankMemorable Member
2 years ago

Thank 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!?

  • chris__1's avatar
    chris__1
    Icon for Advocate II rankAdvocate II
    2 years ago

    Element115 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...

  • Joshrodgers123's avatar
    Joshrodgers123
    Icon for Advocate V rankAdvocate V
    2 years ago

    I'm not sure I understand your reply. What did support say was the workaround and what did they say was by design?