We are also related issues, see https://community.databricks.com/t5/get-started-discussions/databricks-connect-13-1-0-limitations/td.... However, this issue also highlights that the heartbeat that let you know a job was running on Databricks Connect V1 is now missing. For long jobs, it's difficult to tell whether the session has stalled or if there is an active job running. Is there any configuration to enable some heartbeat logging in V2?