- We assume that we have a nested job chain, i.e. a job chain with other job chains in its nodes
- The first node will be skipped for example.
- The JobScheduler returns an <ok/> after the command
- Afterwards a <show_job_chain job_chain='...'/> returns the attribute action="next_state" on the corresponding node.
- So far so good but an added order...
- goes to the first node of the first inner job chain job_chain1.
- The order hangs at this node. The job at this node doesn't get a task.
- if a node of a nested job chain has the attribute action="next_state" then an order skips this node and goes to the next_state node (job_chain2 in above example).
- This issue is not intended for immediate implementation. Analysis results in the assumption that major risks are involved with a fix to this problem.
- Please vote for this issue and let us know if this functionality meets your real-world requirements.