Details
-
Fix
-
Status: Released (View Workflow)
-
Minor
-
Resolution: Fixed
-
1.12
-
None
Description
Current Situation
When having a job chain with more than one node and a suspended order in a node after the start node, then when changing the job chain configuration file while JobScheduler is running the order will be moved to the start node of the job chain.
When changing the job chain configuration file while JobScheduler is not running the order remains at the node and will not be moved to the start node of the job chain.
Desired Behavior
When having a job chain with more than one node and a suspended order in a node after the start node, then when changing the job chain configuration file while JobScheduler is running the order should not be moved to the start node of the job chain. The order should remain at the node where it is.
The behavior when changing a job chain configuration file should be the same when JobScheduler is running or JobScheduler is not running.
Maintainers Note
If the node no longer exists the order will be moved out of the Job Chain, the Order will be assigned to the Job Chain either JobScheduler is restarted or order.xml file is updated manually.