Using the API or Apex, you can send single emails to a maximum of 5,000 external email addresses per day based on Greenwich Mean Time (GMT). Once the limit has been reached, all subsequent emails will fail to send. The emails that failed while the limit was hit must be re-sent after the limit is refreshed at midnight GMT the following day.
The Signature Success plan’s Proactive Monitoring product will monitor for, and alert you to high consumption against this limit. This article outlines some scenarios to help you investigate should you receive an alert. Also, on the Salesforce Help site Designated contacts and above can see your realtime metrics, alerts & more.
If you receive the following error message(s), your organization may experience performance issues and possible service disruptions.
Full error message text:
Note: The Salesforce core infrastructure is set up to facilitate inter-office communication among employees and is not intended for marketing purposes.
Below are some possible scenarios that may result in this limit being hit:
Here are a few suggestions and resources that may help to resolve the 'Single_email_limit-exceeded' error:
When you email internal users, specifying the user's ID in 'setTargetObjectid' will not count towards the daily send limit.
Disable trigger execution during large inbound and outbound data loads. Uploading large volumes of data can cause automated email sends to trigger and can result with your limit being exhausted quickly.
Depending on your qualified Salesforce organization edition, specific governor limits are in place for number of contacts per email and number of emails per day. When you exceed either of these limits, you will encounter one of the aforementioned errors and be unable to continue with your email sends.
Every email address in each individual outbound field (TO: CC: BCC:) will count towards your daily limit. Duplicate email addresses will count towards your daily limit.
Salesforce has a restriction to 25MB for all incoming and outgoing emails. For attachments that contain binary code only, please refer to Create a Batch with Binary Attachments for further guidance.
000382440

We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.