Lakehouse table error : Encountered Azure error while accessing lake file

[Damiensize]

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
 

[Anonymous]

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

[Damiensize]

The user looked at the report 8 hours after the pipeline refreshing the lakehouse data ran.
Same error again this morning, and resolved with the same easy actions : Open semantic model, edit table, confirm.

Error message modal from any visual see details link: