New version of Process, without affecting current instances

[Former Community Member]

Hi,

We have a Long lived Process in Production.

I have noticed that if a new version of that process is deployed, that any live instances of that Process will start using the new version.  i.e. Any processes that have not completed.

I am just trying to work out what the best practice is to update a process version in Production?  Is there a way to ensure that any existing process instances complete using the version they were created with?

Should I:

- deploy a new process, and just try to allow for existing processes instances to stall or fail?

- Try to create a new Application version, or parallel version of the processes running side by side. 

If there is not a simple answer, then I see this as a major gap in the current Process Management implementation.  Any thoughts would be appreciated.

Thanks

[Former Community Member · Accepted solution]

Any instances of the process that are in progress will continue on the version that they were started with. Any new instances will use the new one. Once the last "in process" instance is completed that version is purged.

Paul

[Former Community Member]

Thanks Paul, just to confirm you mean a new Application Version, not a new Process Revision.

I can see that if I update a process revision, then the existing process instances will start to use the new revision.

A new Application version seems to close out the old processes

Please confirm .. thanks

[Former Community Member]

Yes that is correct.

Paul