--- schema_version: "1" id: 76c874f9e4940779266f1949ae3133b9ae65a452487cd7fad2c1d5e557ed995b title: Email Log Considerations and Limits collection: admin version: current locale: en-us portal_url: https://docs.salesforce.com/admin/current/en-us/sales/264-0-0/emailadmin_emaillogs_considerations.md canonical_url: https://help.salesforce.com/s/articleView?id=sales.emailadmin_emaillogs_considerations.htm&release=264.0.0&type=5 source_site: help.salesforce.com content_type: documentation content_hash: 7999338691c4f0ca5e72e7829857d596698a1cddf6eb30b857ff42ae7e220c21 description: Before you request an email log, review request limits, what an email log includes, and when log data can be incomplete. Email logs help Salesforce admins investigate the delivery of email sent through Salesforce, but email logs aren't an audit record. products: - Sales Cloud - Cross Cloud - Service Cloud Voice release: "264" --- # Email Log Considerations and Limits Before you request an email log, review request limits, what an email log includes, and when log data can be incomplete. Email logs help Salesforce admins investigate the delivery of email sent through Salesforce, but email logs aren't an audit record. ### Required Editions
Available in: Lightning Experience and Salesforce Classic
Available in: All Editions except Database.com
## Email Log Capabilities and Limits Email logs provide details about email delivery for email sent from Salesforce. For example, if a recipient states that they didn’t receive an email sent via an email action, request an email log to investigate the delivery status. Email logs use the same search indexes that Salesforce Customer Support uses. However, due to their limitations, email logs aren’t an auditing tool. Those indexes can be incomplete, and successfully delivered emails don’t always generate a corresponding log line in the email logs. ![Warning](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-sales-sales_productivity-264-0-0-production-enus/b2f6c36a-fa61-4a3c-9752-032ce1818a69/images/icon_warning.png) Warning Don’t use email logs for audit, compliance, or legal evidence. ## Email Log File Content and Storage Email logs include inbound email and outbound email sent through Salesforce. Outbound email includes email sent through email actions, list email, and mass email. The logged outbound emails include email sent by all users through Salesforce, including Experience Cloud site users. ![Note](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-sales-sales_productivity-264-0-0-production-enus/b2f6c36a-fa61-4a3c-9752-032ce1818a69/images/icon_note.png) Note Emails sent through external systems such as Gmail or Office 365 don’t appear in email logs. Each email log line includes details about the sender and recipient, date and time, delivery status, and any associated error codes. For field definitions, see [Email Log File Fields](https://help.salesforce.com/s/articleView?id=sales.email_logs_format.htm&release=264.0.0&type=5 "Use the fields in an email log file to investigate email delivery status, errors, security, and authentication."). Email log files count toward your org’s file storage limits. Email logs are CSV files inside a compressed file. Each compressed file contains up to 100,000 records. Because a request can return up to 500,000 records, each request can generate up to five .zip files. ## Missing and Duplicate Email Log Lines To protect performance during periods of high activity, the logging system can omit lines. Email logs aren’t an auditing tool, so a missing line doesn’t necessarily indicate a delivery issue. A reception line without a later permanent-failure or delivery line usually means that the logging system omitted the line, not that Salesforce lost the email. Two identical email log requests can yield different results, even if you run the requests simultaneously. This behavior happens when the tool returns a partial result because a temporary search index is unavailable. ![Note](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-sales-sales_productivity-264-0-0-production-enus/b2f6c36a-fa61-4a3c-9752-032ce1818a69/images/icon_note.png) Note When the logging system omits lines, Salesforce Customer Support can’t recover the missing lines. Email logs can contain duplicate lines. To avoid omitting a line erroneously, the logging system can write the same line twice. ## Email Log Request Limits and Access Email log requests have these limits. - You can request an email log for email sent from Salesforce only within the last 30 days. If a request fails, you can’t resubmit requests that require data older than 30 days. Submit a new request with an adjusted date range. - Each email log can span up to seven days and include up to 500,000 records. To review email logs for more than seven days or for more than 500,000 records, create multiple requests. - You can have up to three pending log requests at one time. Resubmit requests count toward your maximum pending log requests. If you have three pending requests, wait until at least one request completes before you submit another. Users can download an email log only from a Salesforce org that they can access. To get an email log file from an org that you can’t access, such as a sandbox, contact your Salesforce admin. #### See Also - [Check the Delivery Status of Email Sent from Salesforce](https://help.salesforce.com/s/articleView?id=sales.email_logs_edit.htm&release=264.0.0&type=5 "Request an email log to investigate the delivery of email sent through Salesforce in the last 30 days. Email logs support general troubleshooting and delivery analysis, but occasional limits on data availability make them unsuitable for audit, compliance, or legal evidence.") - [Email Log File Fields](https://help.salesforce.com/s/articleView?id=sales.email_logs_format.htm&release=264.0.0&type=5 "Use the fields in an email log file to investigate email delivery status, errors, security, and authentication.")