Forum Discussion

Matthew_Martell's avatar
Matthew_Martell
Icon for Helper II rankHelper II
22 days ago
Solved

Session diagnostics error

Hi Since the June 2026 version of power BI, if I enable 'Start Diagnostics' in the Tools menu of Power Query (for Query Editor only), I get an error when I refresh the data preview: Container e...
Need Help
  • v-abhinavmu's avatar
    v-abhinavmu
    14 days ago

    Hi Matthew_Martell​,
    Thanks for confirming that the issue also occurs in the August 2026 release.

    Microsoft’s documentation explains that Start Diagnostics records evaluations triggered during actions such as Refresh Preview, while Diagnose Step performs a separate evaluation for the selected step. 

    Since the "0x80131623" error persists when using Start Diagnostics -> Refresh Preview, I recommend reaching out to Microsoft Support for further investigation. You can provide them with the affected Power BI Desktop versions, the error code, and the observations already confirmed in this thread.

    You can submit a support request from Power BI Desktop -> Help -> Support -> Submit a ticket, or use the Microsoft Learn link below:
    Create a Fabric and Power BI Support Ticket - Power BI | Microsoft Learn

    For more details, please refer to the below Official Microsoft Documentation:
    Query diagnostics - Power Query | Microsoft Learn
    Record Query Diagnostics in Power BI - Power Query | Microsoft Learn

    I hope this helps. Please feel free to reach out if you have any further questions.
    Thank you.

Matthew_Martell's avatar
Matthew_Martell
Icon for Helper II rankHelper II
7 days ago

I received a reply from Microsoft support after raising a ticket:

"This is a known behaviour that our Product Group has already identified and is actively working on. The behavior is caused by a regression related to diagnostics tracing in the Power Query engine in recent Power BI Desktop builds. Based on the information currently available, the issue is not caused by your report, your data source, or your environment.

I realize that knowing this is a product issue does not remove the inconvenience it is causing you, but I hope it at least provides some reassurance that you do not need to spend additional time troubleshooting your report or environment for the underlying cause.

Unfortunately, we cannot provide an ETA for the permanent fix because the work is still in progress."

v-abhinavmu's avatar
v-abhinavmu
Icon for Community Support rankCommunity Support
3 days ago

Hi Matthew_Martell​,

Thank you for the update and for sharing the information provided by Microsoft Support.

It is helpful to know that the behavior has been identified as a regression related to diagnostics tracing in the Power Query engine and that the Product Group is actively working on it.

Thanks again for sharing the Support findings and the additional details. This information should be helpful to others experiencing the same behavior.

Best regards,
Abhinav