Running orders of a distributed job chain should have all volatile information even if the order is processed by a cluster member that is not JOC's current Master

Current Situation

• JOC Cockpit communicates with one JobScheduler Master member of an active cluster.
• A distributed order can be processed by a member of the active cluster which is not the current Master used with JOC Cockpit.
• JOC Cockpit tries to retrieve the volatile information of a running order from the current cluster member
• This information can be incomplete (e.g. start time is missing) because it is not the member where the order is currently processed.

Desired Behavior

The web services which sends the volatile information about an distributed order should ask the member where the order is currently processed.