scheduler_file_order_sink returns empty set_state

Current Situation

• When the end node for a file order source job chain is scheduler_file_order_sink, the end state in JOC is empty.
• Screenshot
• 

• Order history log

  
  2016-04-29 17:00:30.208+0200 [info]   (Task JS-1627/job1:3323121) SCHEDULER-842  Task is going to process Order JS-1627/job_chain1:c:\tmp\123.txt, state=1, on JobScheduler 'http://MP:4410', Order's Process_class
  2016-04-29 17:00:30.209+0200 [info]   (Task JS-1627/job1:3323121) 
  2016-04-29 17:00:30.209+0200 [info]   (Task JS-1627/job1:3323121) Task JS-1627/job1:3323121 - Protocol starts in C:/ProgramData/sos-berlin.com/jobscheduler/jobscheduler-x64-1.10/logs/task.JS-1627,job1.log
  2016-04-29 17:00:30.220+0200 [info]   (Task JS-1627/job1:3323121) SCHEDULER-726  Task runs on this JobScheduler 'http://MP:4410'
  2016-04-29 17:00:30.220+0200 [info]   (Task JS-1627/job1:3323121) SCHEDULER-918  state=starting (at=never)
  2016-04-29 17:00:30.224+0200 [info]   (Task JS-1627/job1:3323121) SCHEDULER-987  Starting process: "C:\WINDOWS\TEMP\\sos-11E4144D5FC.cmd"
  2016-04-29 17:00:30.273+0200 [info]   (Task JS-1627/job1:3323121) [stdout]  
  2016-04-29 17:00:30.273+0200 [info]   (Task JS-1627/job1:3323121) [stdout] C:\ProgramData\sos-berlin.com\jobscheduler\jobscheduler-x64-1.10>echo hello world  
  2016-04-29 17:00:30.273+0200 [info]   (Task JS-1627/job1:3323121) [stdout] hello world
  2016-04-29 17:00:30.275+0200 [info]   (Task JS-1627/job1:3323121) SCHEDULER-915  Process event
  2016-04-29 17:00:30.278+0200 [info]   (Task JS-1627/job1:3323121) SCHEDULER-843  Task has ended processing of Order JS-1627/job_chain1:c:\tmp\123.txt, state=1, on JobScheduler 'http://MP:4410'
  2016-04-29 17:00:30.278+0200 [info]   set_state success, Job /scheduler_file_order_sink
  2016-04-29 17:00:30.442+0200 [info]   (Task scheduler_file_order_sink:3323122) SCHEDULER-842  Task is going to process Order JS-1627/job_chain1:c:\tmp\123.txt, state=success, on JobScheduler 'http://MP:4410', Order's Process_class
  2016-04-29 17:00:30.444+0200 [info]   (Task scheduler_file_order_sink:3323122) 
  2016-04-29 17:00:30.444+0200 [info]   (Task scheduler_file_order_sink:3323122) Task scheduler_file_order_sink:3323122 - Protocol starts in C:/ProgramData/sos-berlin.com/jobscheduler/jobscheduler-x64-1.10/logs/task.scheduler_file_order_sink.log
  2016-04-29 17:00:30.445+0200 [info]   (Task scheduler_file_order_sink:3323122) SCHEDULER-726  Task runs on this JobScheduler 'http://MP:4410'
  2016-04-29 17:00:30.445+0200 [info]   (Task scheduler_file_order_sink:3323122) SCHEDULER-918  state=starting (at=never)
  2016-04-29 17:00:30.476+0200 [info]   (Task scheduler_file_order_sink:3323122) SCHEDULER-979 Removing file c:\tmp\123.txt
  2016-04-29 17:00:30.498+0200 [info]   (Task scheduler_file_order_sink:3323122) SCHEDULER-843  Task has ended processing of Order JS-1627/job_chain1:c:\tmp\123.txt, state=success, on JobScheduler 'http://MP:4410'
  2016-04-29 17:00:30.498+0200 [info]   set_state 
  2016-04-29 17:00:30.499+0200 [info]   SCHEDULER-945  No further job in job chain - order has been carried out
  2016-04-29 17:00:30.499+0200 [info]   SCHEDULER-940  Removing order from job chain
  

Desired Behavior

• The JOC should show correct end state name success or error.

How to Reproduce

• Deploy attached job chain JS-1627.zip in the JobScheduler's live folder
• create a dummy file in the c:\tmp\123.txt
• Check the JobScheduler order history log and JOC.