Recently we started experiencing blocking errors when completing statuses for task activities which are followed by call activities; this happens for process instances started before the upgrade from v5 to v6 and only started happening after the existing process definitions have been redeployed for v6 compatibility.
Before the redeploy, those processes kept running fine even after the upgrade. Could it be that starting a sub process in V6 from a V5 running process is not supported and if this is the case, which are the options to solve this issue?
- suspend the newly deployed process definition again so the call activity will use the v5 version again?
this didn’t seem to work immediately, but might need better testing
- try the process instance migration -> https://www.flowable.org/docs/userguide/index.html#_process_instance_migration_experimental
would this be a possible solution and is it advisable?
the redeployed process definitions are exactly the same as before, only redeployed for v6 compatibility
Are there any other options?