Deployment conflict with running cronjobs

Active cronjobs can get interrupted by deploying new versions of a Drupal site. Either because we copy the new codebase while a job is running or because we restart Docker containers.

In most cases, this is not an issue. But if e.g. a drush migrate:import is running and gets interrupted, the migration status remains non-idle and no subsequent migration will be possible until a drush migrate:reset-status gets executed.

Not sure, how we can prevent that from happening. Let's think about it and brainstorm possible solutions.