The JobScheduler Master should continue orders from the first node of a job chain after fail-over

Current Situation

When a permanent order runs with a Primary Master then in case of fail-over to a Backup Master the Order does not get completed and gets stuck in between if the Order is with the Job Chain's first node. 

If the Order completes the first node and starts the second node execution, everything is working as expected after fail-over.

The same situation occurs when the Order is configured to be suspended in case of error with the job chain, or if the Order is configured to be set back in case of error.

How to reproduce

• Create a Job Chain on Primary and Backup JobScheduler Master.
• Start the Job Chain on Primary Master.
• Fail-over Primary Master to the Backup Master (e.g: using Abort option)
• Wait until the Primary Master is not reachable.
• Review the task history for the Order.

Desired Behavior

The JobScheduler should complete the Order while the primary master fail-over to Backup.

 Maintainer Note
Please review the below cases in which the JobChain execution is completed successful and incomplete at the time of failover:

• The order is in an incomplete state: When the Order is started and executed on the first node of the Job Chain and in between if failover happened the order state will not change and sticks to an incomplete state and never change to successful. The order history is incomplete and no not have complete details for execution.

• The order is in a Successful state: When the Order is started and completed the first node of the Job Chain and starts the execution of the second or further node and then if failover happened then the order executes completely and the state will change to successful. The complete order history is available.