Locking issue with queue processor.

General
, , , ,
1

We are facing below lock errors with queue processors and though we see the broken item with below error in admin studio. We could see the case processed and moved to resolved state.

Cannot obtain a lock on instance " ", as Requestor “B--------A” already has the lock.

below is queue processor configuration.

  1. In flow we included the run in background shape and passing queue processor details and lock using property .pzinskey.

  2. In the queue processor activity. We just have call resume flow step and log message step.

This issue is not occurring for the all the cases processed.

2

@KRISHNAPAVANP

I think one user must acquire the lock when the queue processor is running against the same case. I hope the locking strategy is default locking and the user has taken action on the case to release the lock or wait for 30 mins if no actions have taken place once the lock is acquired, that could be the reason it’s occurring in a few cases.

Check if optimistic locking if there are two or more users who need to work on the same case works for you based on your business requirements..

Thanks,