Overview
When a form is submitted, Gravity Forms validates each field before the entry is saved. On multi-page forms, validation runs on each page as the user advances.
Validation falls into two broad categories. Required field validation ensures that a value is provided for required fields. Field-specific validation checks that the submitted value meets any additional rules configured for that field type, such as number ranges or choice limits.
Some field types also perform state validation, which checks that the field’s configuration has not changed between when the form was loaded and when it was submitted. Refer to the State Validation article for more information.
For field-specific validation behavior, refer to the documentation for each field type. For custom validation logic, see the gform_validation filter.
For field-specific validation behavior, refer to the field type documentation, where each field type article includes a Validations section. For custom validation logic, see the gform_validation filter.
Validation Errors Without Field-Specific Errors
A validation error that is not associated with a specific field usually indicates an issue with the reCAPTCHA Add-On. This is expected behavior for bot submissions that do not use JavaScript, as the reCAPTCHA response token is not included in the submission.
When this happens for normal visitors, a conflicting script prevents the reCAPTCHA script from running. It can also occur after an update if the page is cached, because the name of the hidden reCAPTCHA response input is based on a value that includes the add-on version number.
Caching and optimization features in themes, plugins such as WP Rocket and WP Fastest Cache, and services such as Cloudflare’s Rocket Loader have been known to cause this issue. Pages that include forms should be excluded from those features. Refer to the Cache and Script Optimizer Issues article for more information.