Force Undeploy Behavior

The Force Undeploy operation cancels any work-items and process instances for the current version and then removes the components and endpoints for the current version. Force Undeploy is a destructive operation, so use it only if you're certain the process data does not need to be retained. In contrast, a normal undeploy waits for process instances to complete their due course (however long they might take to complete) before removing the components.

Important: Do not perform the Undeploy nor Force Undeploy operation on the BPM product application, which is named "amx.bpm.app" by default. Performing either of those operations on the BPM product application can cause the system to become unstable and/or unrecoverable, possibly requiring a re-creation of the environment.

Force Undeploy only removes the data for the current version of your application. Data for older versions is not affected.

Note: The current version of an application means the currently selected value of the Template Version seen under Applications > Details > General Information.

Force Undeploy also detects whether SOAP/HTTP service endpoints included in an application are shared across its various versions. If an older version needs those service endpoints, Force Undeploy does not remove them. However, this detection requires ActiveMatrix Administrator to have a record of the older versions in its database. You can check this via the Applications > Details > Component Status. If you see components with multiple version numbers, that means AMX Administrator has a record of that many versions.

Note: Do not use Force Undeploy when you see only one version for all the components listed under Applications > Details > Component Status, but you know that older versions are running. Using Force Undeploy in this case will prematurely remove SOAP/HTTP service endpoints and disrupt your older versions.
Next topic: Dependent Applications
Previous topic: Cleaning up Failed Deployments