Continue Job Streams after restart or fail-over of JobScheduler Master

Current Situation

When job streams are running and JobScheduler is restarted or failed-over then the running job streams will not be continued. The reason for this is, that in the case of a JobScheduler restart it could happen that the task end event that will be send by JobScheduler to the plugin could not be consumed by the job stream plugin and therefore the Out Condition of the job has not been executed.

Desire Behavior

After a restart of JobScheduler Master all running job streams should be continued.

Workaround

After a JobScheduler Master restart or cluster fail-over the running job streams can be continued by adding the missing event manually with JOC Cockpit.