Hi @jl1 , Based on the provided information, it seems like your issue might be related to the timeout settings of the dbutils.notebook.run
command or the long waiting time for API responses.
The dbutils.notebook.run
command has a timeoutSeconds
parameter that controls the timeout of the run. If the called notebook does not finish running within the specified time, an exception is thrown. If the cluster is waiting for an API response for a long time, it might cause the notebook to exceed this timeout limit, leading to the termination of the command.
It would be better to consult Databricks support by filing a support ticket.