You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Current Situation
The current implementation of NoParallelExection only guards the parellel execution if the trigger is a "Scheduled" one. That means, that a Job with a Trigger and NoParallelExecution set, does still allow running the job at the same time but with a different trigger.
Proposed Change
The NoParallelExeuction should be set on Jobs and not in a single trigger instance. The aim is to exclusively run one single instance of a job no matter with trigger or triggertype has scheduled the run.
The text was updated successfully, but these errors were encountered:
Current Situation
The current implementation of NoParallelExection only guards the parellel execution if the trigger is a "Scheduled" one. That means, that a Job with a Trigger and NoParallelExecution set, does still allow running the job at the same time but with a different trigger.
Proposed Change
The NoParallelExeuction should be set on Jobs and not in a single trigger instance. The aim is to exclusively run one single instance of a job no matter with trigger or triggertype has scheduled the run.
The text was updated successfully, but these errors were encountered: