(OO) Support Tip: splitJoinTrigger found in BLOCKED state
The splitJoin trigger has been found in a BLOCKED/ERROR state leading to multi instance flows not being completed or OO_SUSPENDED_EXECUTION backlog increases to abnormal values. The multi Instance flow completes the multi instance lanes but never transitions out to next step (in this case ‘resolved’) so it hangs in a constant ‘running’ state. This issue was found in OO versions 10.0, 10.02, 10.20, and 10.21.
This is a known issue and defect QCCR8C24579 splitJoinTrigger found in BLOCKED state. Please see the following KM document published on the SSO: https://softwaresupport.hp.com/group/softwaresupport/search-result/-/facetsearch/document/KM01010517
A hot fix has been created for this issue for OO version 10.22.
Workaround in place:
Manually update the splitJoinTrigger to WAITING by running the SQL below against the OO database:
update [dbName].[dbo].[OO_TRIGGERS] set TRIGGER_STATE='WAITING' where TRIGGER_NAME='splitJoinTrigger'
Please contact Technical Support if you have any other questions or would like a hot fix. Thank you.