Dataflow Gen1 refresh errors

ImkeF · ‎08-01-2024

Anyone else experiencing severe refresh errors on Gen1 dataflows today?

Alternating error messages like:
"Error: PipelineException: Container unexpectedly exited. Exit code: 0xC000012D
or
"Error: Evaluation resulted in a stack overflow and cannot continue"
or
"Error: PipelineException: Container exited unexpectedly with code 0x0000DEAD"

Identical dataflow refreshes fine in a premium capacity.

Imke Feldmann (The BIccountant)

If you liked my solution, please give it a thumbs up. And if I did answer your question, please mark this post as a solution. Thanks!

How to integrate M-code into your solution -- How to get your questions answered quickly -- How to provide sample data -- Check out more PBI- learning resources here -- Performance Tipps for M-queries

Anonymous · ‎08-02-2024

Hi @ImkeF ,

Regarding your question, you were able to successfully refresh the dataflow before today, right? Did you use functions such as 'Table.Pivot()', 'List.Distinct()' in your M code that cannot be folded to the source? This will greatly increase the memory consumption. At the same time, you mentioned that the same dataflow refreshes normally in the premium capacity, but fails to refresh in the shared capacity. This may be the reason for the refresh failure, because the computing power in the shared capacity is not exclusive to you.

Best Regards,
Wenbin Zhou