TIBCO ActiveMatrix Platform 3.3.0 hotfix 24 has the below closed defect - 

==============
TAP-15771

In TIBCO ActiveMatrix BPM setup when upgrading a BPM Application, Administrator 
sets the "Prepare For Undeploy (PFU)" flag to "true" for the components' old 
versions. Previously, Administrator set the PFU flag back to "false" if 
"UNCONFIGURE" task failed during upgrade, thus blocking further upgrade. With 
this fix, Administrator doesn't set the PFU flag back to "false" even if 
"UNCONFIGURE" task fails, thus allowing further Application upgrade to proceed 
successfully.
==============

Prior to this fix, the following error is seen when upgrading a BPM application - 

TIBCO-AMX-ADMIN-012603: Not allowed to deploy the version 'x.x.x.xxxxx' of application 'xxxx' since the older version(s) are not in Preparing for Undeploy state: [x.x.x.yyyyy]. An upgrade from these versions may have failed in the past and that is why they are not in the expected state. If the upgrade to version 'x.x.x.zzzzz' had failed, you may need to force-undeploy it first (work items for this version will be cancelled).

This error can also occur when upgrading TIBCO ActiveMatrix BPM - documented here (https://support.tibco.com/s/article/TIBCO-ActiveMatrix-BPM-product-upgrade-may-fail-while-deploying-BPM-applications). 

TIBCO ActiveMatrix (AMX) Platform 3.3.0 hotfix 24 sets the Prepare For Undeploy (PFU) flag correctly

ALL

TIBCO highly recommends using AMX Platform 3.3.0 HF 24 with AMX BPM 2.2.0, 3.0.0, 3.1.0, 4.0.0, 4.1.0 & 4.2.0. Applying this hotfix ensures the PFU flag will be set correctly for all future upgrades. 

This fix is already included in AMX BPM v4.3.0. 

https://support.tibco.com/s/article/Hotfix-TIB-amx-3-3-0-hotfix024-is-available-for-TIBCO-ActiveMatrix-R-BPM-2-2-0-4-2-0-and-TIBCO-Business-Studio-BPM-Edition-3-6-0-4-2-0