It's perfectly fine to not run updateGeneratedJobs, but not running updateTemplates will cause problems if a new template is referenced. What you're essentially doing is disable the managing of jobs AND the managing of templates. We'd probably want to separate this to two check boxes. My other concern is that when someone checks manageJobs and then un-checks it, and then possibly re-checks it. We'd need to be resilient to this kind of change. I think it's reasonable to drive updateGeneratedJobs by the manageJobs. But also driving updateTemplates has too many edge cases.

Would you mind just taking the updateTemplates outside the if statement? And create another pull request if you want to add another checkbox to control template management (along with fixes for the cases where someone disables and enables it over time).