When a Workflow Rule or Process Builder automation in Salesforce is configured to send an Email Alert to a Contact or Lead, the Bounce Management feature — configured under Setup > Email > Deliverability — does not update the IsEmailBounced flag on the record when the email bounces. This is the expected platform behavior. Bounce Management (the bounce alert indicator next to the Email field on a Contact or Lead record) only applies to emails sent manually and directly from a Contact or Lead record by a Salesforce user.
Note: Workflow Rules and Process Builder are deprecated as of the Spring '23 release. Salesforce recommends migrating all automations to Salesforce Flow.
This behavior is standard functionality and working as designed. If an organization has a Workflow Rule or Process Builder configured to send out an Email Alert on the Contact or Lead object, the process will not utilize the Bounce Management feature. Bounce Management works with emails sent directly from the Contact and Lead record by a user. However, if the receiving email address is invalid, the sending address will receive a Mailer-Daemon bounce notification from Salesforce.com — a notification sent automatically by a mail server when it cannot deliver an email — if these emails are not blocked by the receiving mail system.
This behavior applies specifically when the reply email address in My Email Settings is on the salesforce.com domain. If the email address is changed to a non-salesforce.com domain (such as gmail.com), the IsEmailBounced field on the Contact or Lead record is set to True in the same scenario.
Since Workflow Rules and Process Builder are deprecated, consider recreating email alert automations using Salesforce Flow. Flow provides more robust control over email actions and better integration with Bounce Management features in future releases.
000385700

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.