A deployment triggers suspended process instances

Hi guys,

We have an application running with BPT in it. in some process instances an error occurs and the instance is suspended (which is intended).

However, I noticed that when deploying something to the production environment the suspended instances are triggered to resume execution. Is this intended as well?

If so, is there a way to make sure that the instances are not triggered, so that the process instances remain suspended?

Thanks in advance!


Hi Tim,

Your experience is the opposite of what this idea is describing:


Are you talking about processes that where already suspended prior the deploy, or as part of the deploy?



Hi Daniël,

The process instances were already suspended due to errors. This works as designed if you ask me. The weird thing is that a deployment of the module containing the BPT seems to resume the suspended process instance. 

Hi Tim,

I have recently been described this occurrence in a customer, exactly like you described it. But after attempting to create a smaller proof of concept we were unable to replicaet it. I've also opened a support case as I was searching for community posts on the topic when I found yours. Would you kindly share your findings?

Thank you,


Community GuidelinesBe kind and respectful, give credit to the original source of content, and search for duplicates before posting.