My Account | Internet Creations
Welcome, Guest.

The apex class E2CP.ProcessMessage failed due to: System.LimitException: Too many SOQL queries: 101

Symptoms

You are using Email to Case Premium and have received an error email similar to the following:
 
An error occured while trying to deliver the attached email.
You may wish to report the following information to the owner of e2cpremium@22-34sf71dv8fpl4abcy42can5dmk4e3lk3koqyayfs57avhoc9ofj.a-zluhmao.na10.apex.salesforce.com.

The apex class E2CP.ProcessMessage failed due to: System.LimitException: Too many SOQL queries: 101

The attached email could not be processed because the Apex class E2CP.ProcessMessage failed.

System.LimitException: Too many SOQL queries: 101

Class.XXXXXXXXXX
Trigger.XXXXXXXXXX

Solutions

Salesforce governor limits currently allow up to 100 SOQL queries per transaction per namespace. Additional documentation on governor limits can be found here.

As the first step in troubleshooting this error, check the stack trace at the bottom of the error email to see which Apex Classes / Triggers were last executed when the SOQL query limit was exceeded.
  • If the Apex Classes or Triggers include the namespace reference "E2CP", please open a support case with Internet Creations support by sending an email to e2cpremium@internetcreations.com and provide us with the full error message you had received.
  • If the Apex Classes or Triggers do not include the namespace reference "E2CP", this error was likely caused by SOQL query usage exceeded either in the local (default) namespace or within the code execution of a separate managed package.

Apex Classes and Triggers can be located via Setup > Develop. After locating the Apex Classes / Triggers which match the error message, first check to see if they are associated with a managed package by looking for the envelope symbol with the blue arrow pointing down next to the Class / Trigger name. Once they are located, check the Last Modified By field to see when the code was last modified and by whom.
  • If the problematic Apex Classes / Triggers are tied to a separate managed package, please open a support case directly with that ISV and provide them with a copy of the full error message you had received.
  • If the problematic Apex Classes / Triggers are found to be local to your Salesforce Org, please reach out to your development team or the user who had last modified the code to further review its SOQL query logic.

Note: Internet Creations support cannot assist with governor limit errors caused by code running outside of what comes packaged with Email to Case Premium. However if you require further assistance with updating the SOQL query logic within your local code, please contact your Internet Creations Account Executive to inquire about professional services.
 

Status

Additional Information

Support

Open a Case