Broker Failure

If a client is disconnected from the Broker and the connection times out, the client resubmits outstanding reservation tasks to the new Broker as soon as it can log in.

It is possible that this is due to the Client-Broker connection broken, but the Broker is not down and Engines are still connected and running tasks.

If the Driver timeout is set the same on the Broker and the Driver, the Tasks on the original Broker are canceled, so the existing connections are closed and the Service fully recovers.