Details
-
Feature
-
Status: Released (View Workflow)
-
Major
-
Resolution: Fixed
-
None
-
None
-
None
Description
- Current Situation
- In a job chain with e.g. three job nodes an order is waiting to run at the top state. When adding a new job node and state between the first and the second job node then the order executes the new job node on the next run.
- If a user were adding a job node and state as the first state of the job chain, i.e. making it the top state, then the order ignores the newly added job node until JobScheduler is restarted.
- Desired Behavior
- Adding a new job node to the top of the job chain should modify the order's assignment to the job node that was the first node at the time when the order was updated the last time.
