Hello, the subject says it all.

We are using version 8.4.0 and we had this behavior in previous versions as well.
Let's say we have Job1 with this flow: On success, Run Job 'Job2'. If we disable Job2, it will run anyway after Job1 succeed.

In my mind, when we disable a job, it is because we don't want it to run.

Thanks!

I see your logic and have seen this myself.
We get around this by either removing the job from the environment (as it is disabled anyway!) or disabling all tasks in the disabled job.

Yes, currently this is seen as a "feature" but we will probably change this behavior.

---

Please give us a warning before changing this behavior as it will break some of our processes if it changes without warning! We have many jobs that expect and use this functionality.

Thank you.

Please give us a warning before changing this behavior as it will break some of our processes if it changes without warning! We have many jobs that expect and use this functionality.

Thank you.

Yes, we will probably add an option here so you can control the behavior.

---