Status of Job Stream instances should switch automatically

Current Situation

Job stream instances are automatically qualified as "running" or "not running". The rule to identify a running job stream instance is:

• There is at least one local event - not a global event - available with the In Conditions of a job stream that has not been consumed and the event is created by a local Out Condition then the job stream instance is considered being running.

• If not all In Conditions of a job stream have the checkbox Evaluate once and prevent duplicate job starts checked then this rule fails. The job stream instance remains in running state.

Desired Behavior

The mechanism to qualify a job stream instance as not running should work even if not all In Conditions have the checkbox Evaluate once and prevent duplicate job starts checked.

Patch

A patch for this issue is available here