Problem: The execution are cancelled automatically when new version of integration is published

[muhilvarnan-v]

HI,

Currently i have workflow defined with application integration. the workflow has a step for `suspend task`.

with this workflow i have 10 to 20 executions created and most of them are paused because of the suspend task. 

now if i want to make changes to my workflow by adding some additional steps or configuration change. i have create a new version and publish version. once i publish, the current executions which are waiting suspend is also get cancelled and there is no option to resume from that step. 

this way for cancelling the executions will bringing down value of the true power of suspend task. 

please let me know, if someone have faced this issue before and if there is any work around.

[fengwan · Accepted solution]

This behavior is actually by design. When you execute an integration, you are executing the current definition of the integration. When you publish a new version, you also unpublish(decommission) the old version. Therefore we cancel all the pending executions related to the old version. This is also for safety purpose since the executor might not be the publisher.

If you don't want the old executions to be cancelled, you could create and publish a new integration with changes. Let me konw if it makes sense.