Forum Discussion
400 error when accessing lakehouse files from notebook
Hi SørenBrandt
You may try reading the CSV file with ABFS path instead and check whether this will be more reliable. This could avoid failures in a scenario that the default lakehouse might be changed.
Best Regards,
Jing
Community Support Team
I too have seen this behavior with the default lakehouse. In my case, it seemed to be cuased by another operation outside of Fabric processing the file, so to speak. The csvs in my case are written by an external service within Business Central, which runs every 2 hours. I needed to ensure that my notebook is only run after the write operation completed. If the file was being written while the notebook was being run, I would get this error.
Hope this helps!
FilipAiHelper I
Excellent - thanks for pointing this out. I had the exact same scenario happening to me, and didn't think about that.