+ Start a Discussion

UNABLE_TO_LOCK_ROW doesn't included record Id.

The UNABLE_TO_LOCK_ROW which can make debugging almost impossible in a complex application.  I don't know if this is intentional or not but it seems to me that if the server detects deadlock (or timeout), it knows the record ID and could just as easily put it in the message.


If you know a way to get the ID, I would be call to let me know.


If there is no way to get the ID, vote for the idea on Ideas--


https://sites.secure.force.com/success/search?type=Idea&keywords=UNABLE_TO_LOCK_ROW: https://sites.secure.force.com/success/search?type=Idea&keywords=UNABLE_TO_LOCK_ROW