Oauth2 gateway bugs affecting datasets not dataflows (WHY IN 2024)

After two months of waiting for Microsoft to provide support to Mindtree, they finally came back with the following response.  It covers the mid-stream oauth-refresh bugs, and the deprecation of GEN 1 dataflows as well.

Quote:

Yes, the Gen 1 Dataflows will be deprecated but unfortunately, we don’t have an ETA for it. However, this is one of the reasons why the PG has discontinued “mid-stream token refresh” in the Dataflows Gen1.

... 

midstream token refresh is completely discontinued from Dataflow Gen 1 and the product team will no longer support it. This is a product limitation when using Dataflows Gen 1.

If there was any doubt, Power BI customers should begin abandoning GEN1 dataflows for the more expensive GEN2 variety.  I have found the costs to be substantially more... this is primarily because GEN2 dataflows will also charge for (1) the passage of time, and (2) the use of the self-hosted on-premise gateway.  When accounting for those things it leads to far more CU consumption than before.  With GEN1 dataflows we seemed to be paying only for the actual compute (vcores) that is used in our premium capacity.   But with GEN2 they have found other meters to to use, in order to rapidly decrement our CU's.