Forum Discussion
Dataflow Gen2 - failing to load into the lakehouse
Hello, thanks for taking the time to answer. I already verified that the naming rules are respected. Also, if naming issues were actually behind the failures, I would expect a consistent pattern where the refresh fails everytime. But since this is intermittent, without any edit in the queries in between, I am inclined to rule out the naming. I have the request ID written down but I could not find any error logs besides the one reported in my post.
- v-saisrao-msft3 months ago
Community Support
Hi Mauro89,
Thanks for confirming. Since you've already verified the documented naming requirements and the failures are intermittent across different tables without any query changes, this doesn't appear to match a typical naming validation issue. As an additional isolation step, you could test writing the same Dataflow Gen2 output to a new Lakehouse or a new destination table to determine whether the behavior is specific to the current destination. If the issue persists, I'd recommend opening a Microsoft Support case and providing the captured Request ID, as the available documentation doesn't describe this intermittent WriteToDataDestination/Lakehouse036 behavior and further investigation may require backend diagnostics.
Create a Fabric and Power BI Support Ticket - Power BI | Microsoft Learn
Thank you.