Skip to content

A BPA workflow that's been deployed (even with no projection or event connected to it) can't be deleted — the Delete option fails because there's an active version, and there's no visible option to deactivate that version first.

Answer

From 22R2 onward, there's an Undeploy command for BPA workflows that deactivates the currently active version, which then lets you actually delete the workflow afterward — this is the intended path for fully removing a workflow that's already been deployed at least once. On earlier releases without Undeploy available, there isn't a confirmed client-side way to deactivate an active version yourself; that scenario may need a support case.

← Browse Workflows and automation questions