You’re running into this because DAB treats the YAML definition as the source of truth — so every time you redeploy, it will reset the job state (including the paused/running status) back to what’s defined in the file. Unfortunately, there isn’t currently a way to negate include so that you can easily exclude just the continuous job from deployments.
The common workarounds are:
Split the continuous job into a separate bundle so it’s managed independently of the scheduled jobs.
Use include explicitly for the jobs you want to update, even though it requires maintaining the list.
Or, manage the continuous job outside of DAB if its state needs to be controlled dynamically (e.g. via notebook or API).
At the moment, DAB doesn’t support excluding resources by default, so either separating resources into different bundles or explicitly including what you want are the only reliable options.
Yogesh Verma