If remote configuration client uses http://[jobscheduler_host]:[jetty_port] for the supervisor attribute and the connection to the URL fails when the client starts then client goes into the state "wait_for_activation"

If you start a remote configuration client uses http://[jobscheduler_host]:[jetty_port] for the supervisor attribute and the connection to the URL fails then the client goes into the state "wait_for_activation". So no jobs etc. are read from the live folder.

If a remote configuration client uses http://[jobscheduler_host]:[jetty_port] for the supervisor attribute already running and the the remote configuration server is down then the client is furthermore running. That's OK.

The remote configuration client runs nevertheless if the remote configuration server is down when it is configure in the supervisor attribute without http protocol. That's OK.