[SalesForce] Query of LOB fields caused heap usage to exceed limit

I understand that this has been asked many times before. But I haven't been able to find a conclusive answer or guide to solve the issue.

When we add a new product to an opportunity we get the following error.

Apex trigger npsp.TDTM_Opportunity caused an unexpected exception, contact your administrator: npsp.TDTM_Opportunity: System.LimitException: Query of LOB fields caused heap usage to exceed limit.

This has only just recently started occurring after 12-months of usage – and the person who originally developed this for us is not longer available.

As a not-for-profit, we can't exactly go out and find another developer to amend this for us, so any help would be greatly appreciated.

Best Answer

As sfdcfox mentions, the Power of Us Hub is the best resource for NPSP support -- it's a very active community of NPSP users, consultants and the actual NPSP developers in the Salesforce Foundation.

There was a post about this error just last month. In their case, it was related to a large NPSP error log, so they purged the log (NPSP Settings > System Tools > Error Notifications) and the error went away. Apparently, inserting an opp causes a query on the error log object and that was causing their heap error.

Related Solutions

[SalesForce] Attachment Cloning: System.LimitException: Query of LOB fields caused heap usage to exceed limit

There's no need to clone the records, since you can just reset the id field by assigning null.

for(Attachment temp: attList) {
    temp.Id = null;
    temp.ParentId = newParentMap.get(temp.ParentId);
}
insert attList;

[SalesForce] APEX Heap size and limit Confusion

As I discovered when investigating Does execute anonymous from Developer Console not enforce heap size limit?

The support rep responding to my case told me:

heap size checks are performed according to certain heuristics, meaning they are not performed on evaluating each statement, and as a result it is possible to exceed the limit, but this will be enforced as soon as salesforce checks it.

Also note that they will not share the specifics of when it will be checked:

I had a discussion with my seniors regarding the evaluation of heap size as how it works internally but the architecture and internal implementation details cannot be shared.

As explained previously we follow certain heuristics to determine when to compute the heap size (which performs a heap walk), and when to enforce the max heap size, which doesn't occur when invoking Limits.getHeapSize().

Best Answer

Related Solutions

[SalesForce] Attachment Cloning: System.LimitException: Query of LOB fields caused heap usage to exceed limit

[SalesForce] APEX Heap size and limit Confusion

Related Topic