“What The Heck Does This Error Mean?” Simple Explanations of Common Errors

Apex Error

If you know how to troubleshoot a few common Apex errors, you can resolve issues faster.  Technical Architects and Developers will love you for not asking them as much.

Furthermore, If you can teach your users what some of the Apex and other common errors mean, they might be able to resolve something on their own without coming to you.  

Here are some phrases to look for.

 “Attempt to de-reference a null object”

  • Most often, this means that a record involved in the process is missing a key piece of data referenced in the code.

  • It could also mean the user who triggered this process doesn’t have access to a field, object, or record type.



  • There is a validation rule preventing the record from being updated.


“System.LimitException: Too many query rows: 50001

  • You get this error when when Apex Code tries to query more than 50,000 records, which is the Salesforce limit for Apex.
  • Solution:  Try to use more filters in the search. A code update may also be needed


Other “Exceptions”


“Insufficient Privileges”  

  • The user doesn’t have access to edit or view a record.
  • Could also happen due to a lack of user permissions


“Insufficient access rights”  -or-  “Invalid access rights on cross reference ID”

  • Basically, this is the Data Loader version of Insufficient Privileges.


“ID value of incorrect record type”

  • Another Data Loader error, caused by a funky ID on your source file.
    • Check your ID’s, are they valid?
    • Could also be that you mapped a text column to the Salesforce ID column.


“Your account has been disabled”  (The dumbest error)

  • It happens on Approval Processes and has nothing to do with the user who received the error, but they’ll think it does and come to you quite concerned.

  • What it actually means is that one (or more) of the steps on an Approval Process contains an inactive user on the approver list.


Did I leave any out? Any other tips for troubleshooting errors?  Comment below.

2 thoughts on ““What The Heck Does This Error Mean?” Simple Explanations of Common Errors

  1. Invalid access rights on cross reference ID.
    Occurs when you attempt to set a record ID in a lookup field that is invalid because:
    1) Wrong object (usually occurs with the dataloader)
    2) You do not have permissions to view the object and/or record
    3) You do not have permission to set the record type.

Leave a Reply

Your email address will not be published. Required fields are marked *