Guest Users (also known as Unauthenticated Users or unauthenticated site visitors) trying to use, for example, a Contact Support Form in an Experience Site will be able to submit records with a "submission successful" message even when the input data should have triggered a Validation Rule. However, records will not be created in the system.
When a Validation Rule blocks a Guest User submission, the following email is sent to the system administrator:
Subject: There is an issue with This Case
Salesforce could not create this case because of the reason listed below. We will try creating the case again. For more information about this error or help with Web-to-Case, please contact Customer Support.
Reason: support.cases.WebToCaseException: Error code=FIELD_CUSTOM_VALIDATION_EXCEPTION, message=Hey Guest User! Enter a case reason, fields=[Reason]
Record Information: _quickActionName = NewCase _record = {"Status":"Unassigned","Description":"Test Case Guest User with Validation Rule","Priority":"Medium","Reason":"","Subject":"Test Case Guest User with Validation Rule"}
Thank you!
Customer Support salesforce.com, inc.
The Landmark @ One Market, Suite 300 San Francisco, CA 94105
This is currently working as designed.
The process of creating a case for Unauthenticated Users (also known as Guest Users) is different than the one in place for Authenticated Users.
All validation processing, except checking for non-empty required fields in the form, is done on the server-side. For Guest Users, these Case submissions do not have validation run until they are processed off of the queue. As shown in the error email above, they are submitted as Web-to-Case records to Salesforce.
If you need to add validation criteria before Guest Users can submit cases in an Experience Site, you need to create a custom component to replace the standard Contact Support form. This custom component can enforce validation on the client side before the record is submitted.
000381943

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.