Requestor lock exception having null on requestor ID
Hello, we are facing an issue related to the lock on some cases. The exception is thrown by a Job Scheculer, which resolves cases using pxForceCaseClose OOTB Activity.
Initially, we were getting the Exception so we decided to add logic before calling this Activity. This logic checks the Sys-Lock class using the Instance Handle of the case, if a record exist, then we check if the expiration date is still valid. If lock is valid we are not calling the Activity to close the case. However, even after this logic the exception is still being thrown for a reason we don't know.
Trying to understand the issue we notice the requestor ID displayed on PDC says "as requestor id null...", is this for security reasons? or maybe the issue is on cache or something like that. As additional info, in lower environment (DEV), the requestor ID starts with the Agent Identifier ("B"), like if the case is locked by the same agent.
If any of you have experienced the same issue, could you please share your solutions?
Thanks In Advance.
Bits in Glass
IN
@Gil_BC I have faced a similar issue, but in a different context. I hope you are calling your activity directly within job scheduler. Can you do like this and please check? -> Within job scheduler-> Activity-> Queue-For-Processing-> queue your activity.