Resuming an order in a distributed job chain with <modify_order suspend="false"> should continue that order

Current Situation

• A persistent order is suspended in a distributed job chain when a <modify_order suspend="false"> command is send to the JobScheduler to resume the order and to set the order's state to the next state.

  <modify_order job_chain='Ticket#2016020310000022/job_chain3' order='test' state='200' suspended='no'>
    <params><param name='exit' value='0'></param></params>
  </modify_order>
  

• The order is resumed and moved to the next state, however, the order does not execute but shows the next start time.
• For example:
  • Order has a run time to start every 2 minutes
  • When the start time is reached the order will be moved to the start node of the job chain and will wait for two minutes but will not execute.
• This behavior is not observed when the job chain is not a distributed job chain.

How to reproduce

• Deploy attached example in the live folder
• Let the order Ticket#2016020310000022/job_chain3,test run, the order will be suspended at the state 100
• start the job Ticket#2016020310000022/job_resume, this will resume the order
• The Order will be resumed but will not excuted the job at state 200, also it will show the next start time.

Desired Behavior

• The <modify_order suspend="false"> command should continue the order for the next start time.