Contact us Blog

Common Salesforce error messages

Apsona apps are a layer on top of Salesforce. Therefore, whenever the Salesforce back-end reports an error, Apsona shows the error in the browser or in a downloaded CSV error file. Here are some common error messages you might encounter, along with their causes. Since these are Salesforce errors and not Apsona errors, you might need to track down the exact cause of the error in your org in order to resolve it.

Unable to lock row

This error usually appears in this form:
UNABLE_TO_LOCK_ROW, unable to obtain exclusive access to this record
It usually happens because some other background process - perhaps a trigger, flow, or other integration in your org - has the record locked, so the Apsona can't use it. That error is sporadic and usually goes away on retry. A quick Google search shows lots of help on this issue.

Insufficient access rights on cross-reference id

This error can occur if you are trying (directly or indirectly) to update a lookup field in a record, and your profile doesn't have access to either the field or the object to which the field refers. There is no easy way to determine which specific field caused this issue, unfortunately, so you will need to resort to trial and error to find the specific field and then ask your admin to give you access to that field and its refered-to object. This developer forum article might help clarify the issue.

Request limit exceeded

This error usually appears in this form:
REQUEST_LIMIT_EXCEEDED: TotalRequests Limit exceeded
This means that there have been too many API requests to Salesforce from your org. Salesforce counts the total API requests based on all applications installed in your org. The limits are reset every 24 hours. This Salesforce article has more information about the issue. Also see how Apsona shows API usage.