Warning: Call Activity Bug prevents Workflow Redeployment
Hi all,
We’ve worked with Collibra support (ticket #134284) and engineering to finally identify a workflow deployment bug that is causing us a lot of grief, and wanted to reach out
- to give warning of this one, and
- see how many others are experiencing it.
Scenario: (at least with Workflow Designer)
Workflow A uses a Call Activity to call Workflow B
Workflow B has a user task — or other component — may take time to complete.
Redeploying Workflow A causes any instances of Workflow B to crash when they complete:
org.flowable.common.engine.api.FlowableException: Cannot complete process instance. Parent process instance <someUUID> is suspended
This bug It’s scheduled for fix in the 2024.05 release, but that seems like a long time away, given the pains that this is giving us.
Anyone else experiencing this?
Tom Friesen
Posted 2 years ago · Edited 1 year ago·Last reply 2 years ago
1 comment
Elliott Diehm
·2 years ago · EditedLooks like Collibra has an on demand patch available for this: 2024.02.2 - Redeploying a workflow with a sub-process when a user task of the sub-process is still active no longer prevents you from completing the user task. (ticket #134284, 137412)