Hi Ajay,This is expected behavior. A job cluster is designed to be ephemeral, so Databricks creates a new cluster for each run and terminates it when the run finishes. Currently, there isn't an option to keep the same job cluster alive across continu...
