Process suspended after adding noninterrupted timer boundary event on new version deployment

Hi Team,

I had one process there was no boundary event and it was working fine. Then added noninterrupted timer boundary event on same process and deployed a new version. After deployment i saw new version is deployed but it is in suspended state. Could you please let me know why it is happening.

Hi,

By default a newly deployed process definition is active. But there is an optional feature to deploy a model in suspended mode and let the process engine activate it only at a specific time (see parameter deployment-activation-time here in the REST API reference). Maybe you are using that accidentally/unknowingly?

Cheers,
Thorben

Hi,

Thank you for quick response. Removed deployment-activation-time and it worked fine…

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.