Wrong nodes in JOC Cockpit history if job chain has a file_order_sink configuration

Curent Situation

• We assume we have a job chain with a <file_order_sink../> configuration then the wrong node reported in the JOC Cockpit history.

  <job_chain >
      <file_order_source  directory="C:\tmp\fileorder"/>
      <job_chain_node  state="10" job="test" next_state="20" error_state="error"/>
      <job_chain_node  state="20" job="test" next_state="success" error_state="error"/>
      <file_order_sink  state="success" move_to="C:\tmp\fileorderArchive" remove="no"/>
      <file_order_sink  state="error" move_to="C:\tmp\fileorderArchive" remove="no"/>
  </job_chain>
  

• The node in JOC Cockpit is for above example sometimes "10" or "20" but never "success" or "error".
• Further the node can be "10" and the status is "successful" or "failed" but "incomplete" is expected.

Desired Behavior

The correct nodes are to be output