We are currently using Camunda 7.11.0. All of our workflow tasks are currently async before/after.
We have observed that when we suspend a process definition that it seems to suspend all job definitions for that process definition too as a side-effect (according to Camunda debug logs). This seems to be a good thing to us, since suspending a running process instance invariably ends up with the currently-executing job(s) throwing an optimistic locking exception. But with the job definitions suspended, currently executing jobs can complete but no more can start because all the defs are suspended and no OLEs are seen. Resuming the process definition seems to resume the job definitions as well but not any suspended jobs which resulted from the definition suspension. Those have to be resumed separately (and so far that’s fine by us).
My question is this, though: my internet searches and documentation reading have come up empty on this being documented behavior, so is it something we can count on to continue for future releases?