I have a notebook that calls other notebooks with `dbutils.notebook.run` and execute them as a 'Notebook job'. But sometimes when a notebook is taking a long time and the cluster is just waiting for, for instance, an api response, the subsequent commands that are submitted and shown as "waiting to run" just get a "command complete" message without being executed. It seems like the cluster waited (not inactive, as it checks with the api and see if there's a response) for a long time, but gave up on waiting at some point without any warning, and then terminated. the message "command complete" is too vague, and sometimes the notebook job does get executed. i haven't been able to reproduce this situation, it happens occasionally and coincide with the cluster having to wait around for a long time.
