Hi @violeta482yee,
Have you checked the resource availability of the compute attached to the notebook?
One solution could be: to usecloudFiles.maxBytesPerTriggerOption: This option allows you to control the maximum number of bytes processed in each trigger. For example, setting it to 100m will process up to 100 MB of data per trigger. This can help prevent the notebook from crashing due to memory overload
But it requires more investigation on the compute being used to determine the reason.