If the client looses the connection to a job manager and the job recovers from this, the client will only print the job status as RUNNING again. It is hard to actually notice that something went wrong and a job manager was lost.
After 14:35:43 everything is running and the client does not print any execution state updates. When the job manager fails, the job will be recovered and enter the running state again eventually (at 14:40:40), but the user might never notice this.
I would like to improve on this by printing some messages about the state of the job manager connection. For example, between 14:35:43 and 14:40:40 it might say that the job manager connection was lost, a new one established, etc.