Passing multiple comma-separated values against the CONTAINS operator in the same condition doesn't evaluate the Process or Flow as intended.
Example Process:
Set Filter Conditions:
[Case].Contact.Email CONTAINS someone@company.com,someoneelse@company.com
The above example process will not evaluate as intended because it includes multiple values separated by a comma.
Process Builder and Flow do not support comma-separated values in rule criteria. In order to get this functionality to work, the Process/Flow criteria can be modified to only use one value per Filter Condition and add additional Filter Conditions as needed, ensuring that each Filter Condition is grouped together with an OR Filter Condition.
Workaround:
Using the same condition as above:
Set Filter Conditions:
1. [Case].Contact.Email CONTAINS someone@company.com
2. [Case].Contact.Email CONTAINS someoneelse@company.com
Filter Conditions (Customize the filter logic):
(1 OR 2)
Trailblazer Community - Contains on Comma separated value in validation Rule
000386764

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.