In line with security best practices, Salesforce requires that the Default Workflow User, if set, has a verified email address. This article explains why this matters and what happens if the email address isn't verified.
This article explains why Salesforce requires a verified email address for the Default Workflow User, and how to resolve the exception thrown by Workflow Rules or Flows when that email address isn't verified.
If you have Email Alerts configured to use the Default Workflow User and do not verify the email address, users will see an exception when any Workflow Rule or Flow which uses that email alert executes.
If you have Email Alerts configured to use the Default Workflow User, make sure the user's email address and return email address have been verified, as described in Verify Email Addresses to Send Email Through Salesforce. Once the Default Workflow User's email has been verified, no additional steps are needed to fix the affected Workflow Rules or Flows.
000782250

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.