Incoming/Outgoing Referrals Scheduler Error Log - UNABLE_TO_LOCK_ROW

Some users encounter an error when running two automated processes simultaneously—for example, sending a Referral during a Litify managed packaged upgrade. The error message is triggered when one process locks a record (or records) from being changed, which causes the subsequent process to fail, resulting in the following message:

New ERROR Log created (LOG-1811133140).
IncomingReferralsScheduler # dispatch Upsert failed.
First exception on row 0 with id xxxxxxxxxxxxxxxx;
first error: UNABLE_TO_LOCK_ROW, unable to obtain exclusive access to this record: []

This typically occurs during Litify managed package updates, specifically on the Incoming/Outgoing Referrals Scheduler processes. While the record lock triggers an error, the process will resume as expected on the next "retry" (incoming and outgoing retry on an end-user determined time interval) after the process which locked the records is complete. The record lock acts as a safeguard so multiple automations are not changing a record at once.

 

Was this article helpful?
0 out of 0 found this helpful