Action pack upgrade without deactivating current executions

Discussion created by JagdishGidwani609069 on Sep 25, 2017
Latest reply on Oct 6, 2017 by JagdishGidwani609069
Hello All,
We face a problem where on upgrading any action pack i..e installing a latest version on Action pack when lower version was already in use. We frequently get an error while installation that requires current executions to be first deactivated , however as these executions are active in order to allow "Rollback" to be triggered even after few days after deployment.

My questions are
a) Is there anyway we can upgrade Action pack without having a need to deactivate current executions.
b) If a) is not possible , how do we handle Automic upgrades without affecting current deployments which possibly were done recent and after expected to be active at least for 2-3 days.

Thanks for your suggestion / guidance in advance