I do not want previous versions to spawn new instances. But I want the previous instances to complete. There are already many instances waiting in the previous versions. Now I have to manually migrate them to the latest camunda process definition version so that the timer event can proceed for those process instances.
When I check the management service ManagementService (camunda BPM Javadocs 7.3.7-ee) then I only see the latest deployment ID and not the older deployment IDs. I tried to register the older deployment id manually but I get the below error
org.camunda.bpm.engine.context : ENGINE-16004 Exception while closing command context: Deployment “respective deployment ID” does not exist: deployment is null
it could be case regarding the mix of process application and deployment, that the job executor in the process engine didn’t feel responsible for jobs that were created from process definitions deployed by the modeler after a restart of the engine. You can find more details about the background here: The Job Executor | docs.camunda.org