Process changes are not saved

Sirisha N if you are sure that you have done modification to actual process model but not the instance. And you have published the process model but still you are facing this issue, then to debug this, you can delete all the previous versions of this process model and republish this process and try executing that.

Now you will be able to find only that behaviour which you have configured in your current process model version, as this do not contains any other versions than the current one.

Hope this will help you.

Sirisha N if you are sure that you have done modification to actual process model but not the instance. And you have published the process model but still you are facing this issue, then to debug this, you can delete all the previous versions of this process model and republish this process and try executing that.

Now you will be able to find only that behaviour which you have configured in your current process model version, as this do not contains any other versions than the current one.

Hope this will help you.

Hi Alok,It is in production environment so I don’t think it is the correct way to delete the older versions.Can you please suggest me any other solutions?
Thanks,
Sirisha N.

Hi Sirisha, you can remove these multiple versions in Dev, then push it to test followed by UAT, and if all good then deploy this as a patch to production.

So, I don't think there is anything wrong in this approach. I believe this should work for you, unless your licence is not expired, as @Sachin mention Above

However if an object has multiple versions, it consumes that much of memory as well.

I feel you should check for license as suggested by Sachin and also try to take the published process model from your Dev env. and deploy in your higher env. May be this way you will get the updated process model.