Check your eligibility for this 50% exam voucher offer and join us for free live learning sessions to get prepared for Exam DP-700.
Get StartedDon't miss out! 2025 Microsoft Fabric Community Conference, March 31 - April 2, Las Vegas, Nevada. Use code MSCUST for a $150 discount. Prices go up February 11th. Register now.
Hi,
This morning, one of our report using a direct lake model was down. Each visuals were not rendering.
The see details button provided the folowing description of the error :
Error fetching data for this visual
Unexpected parquet exception occurred. Class: 'ParquetStatusException' Status: 'IOError' Message: 'Encountered Azure error while accessing lake file, StatusCode = 404, ErrorCode = , Reason = Not Found'
Please try again later or contact support. If you contact support, please provide these details.
I did resolve this issue by simply opening the data model, opening the edit table modal window, and closing it by clicking on the confirm button.
What it did I guess is refresh the connections between the direct lake model and the lakehouse tables.
Why did I have this issue?
Thanks,
Damien
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Damiensize ,
It may due to the relay. A Direct Lake semantic model refresh operation might evict all resident columns from memory. That means the first queries after a refresh of a Direct Lake semantic model could experience some delay as columns are loaded into memory.
Hope it hepls!
Best Regards,
Community Support Team _ Caitlyn