I have created a simple heartbeat process which fires every 5 minutes. Examining the database I noticed that processes from the previous deployments were still getting started.
Overall for my application I don’t want to run processes from previous versions of deployments.
I tried to solve this particular issue by stopping or suspending the process instances from previous deployments but that seems to result in optimistic lock exceptions.
Is there some way to
- Stop previous deployments from being deployed
- Migrate process instances before the process engine begins executing
- Stop process instances from being deployed?
On my event timer I also tried to configure my start event with:
<startEvent id="startTimer" name="Timer starting heartbeat"> <extensionElements> <flowable:startEventCorrelationConfiguration><![CDATA[storeAsUniqueReferenceId]]></flowable:startEventCorrelationConfiguration> </extensionElements> <timerEventDefinition> <timeCycle>R/PT30S</timeCycle> </timerEventDefinition> </startEvent>
But that doesn’t seem to do what I hope it does when I cause new deployments to be created by changing the process configuration.