Timer Boundary Events of active process instances are suspended when process def is suspended?

I am seeing a behavior that i cannot seem to find in the docs:

Given a active process instance with a task that has a non-blocking timer, when the process def is suspended, the process instance is still active, but the boundary timer gets suspended.

Is this expected? If so, is there docs explaining this?

Doesn’t suspending a process definition suspend all its instances?

@fml2 as per the API as ref: https://docs.camunda.org/manual/7.12/reference/rest/process-definition/put-activate-suspend-by-key/

You can suspend a Def without the active instances being suspended.

@Niall do you have insight on this?

I am thinking it is related to this https://jira.camunda.com/browse/CAM-3986 ?

But does not appear to have any docs related to this behavior https://github.com/camunda/camunda-docs-manual/blob/master/content/user-guide/process-engine/process-engine-concepts.md#suspend-process-definitions

@Niall if this behavior is expected then considering:

"If you have deployed definition, and you want to stop new process instances from being created for that definition, and you want to let the current active instances complete, how does one go about making this happen? "

If it’s not clearly documented, I’d try to figure it out from the code. There lies the truth!

It is not about the code in this case, it is about the underlying impl decisions and how to use within ops.

Hi Folks,
I’ll look into this and see if i can get an answer for you.