@holychs - Well, this behaviour needs troubleshooting I imagine.
- What is the auto-termination value. Try increasing it to much higher value and observe if it is the same.
- Does your workflow have multiple notebook tasks? If Task A finishes while Task B is still running, a glitch in the job contxt can sometime trigger a cluster teardown if the cluster was pinned to the job.
- Does your notebook contains conditional logic that calls dbutils.notebook.exit("Success") ?
- Are you triggering this job manually while someone else is using the cluster?
Also, check the Runs on the cluster. Go to the Compute page -> Select your Cluster -> Runs tab. This will show you exactly which jobs/notebooks were attached to that cluster at the moment of termination.
RG #Driving Business Outcomes with Data Intelligence