Failed validation on field even though not validations exist

Help
1

I’ve got an email field that’s in a record. Any time I make a change it tells me to provide an email even though there is one already in the field. I have no validations on the field except it can’t be null. How do I troubleshoot this? No validations, etc. It’s a brand new field that I set to be required at creation time, but the UI says the value is required when all I’m doing is updating another field and the email isn’t changing. I get this response in the HTTP 400 returned to the PATCH request:

{ "errors": [ { "message": "Validation failed for field \"email\". Value is required.", "extensions": { "field": "email", "path": [], "type": "required", "code": "FAILED_VALIDATION" } } ] }

The request payload looks like this:

  1. {last_name: "abcde"}

But if i update and change the email field along with the last name it works fine. I can’t figure out why it’s requiring me to change that field.

[00:43:03.278] DEBUG: Validation failed for field "email". Value is required. err: { "type": "", "message": "Validation failed for field \"email\". Value is required.", "stack": DirectusError: Validation failed for field "email". Value is required. at file:///directus/node_modules/.pnpm/@directus+api@file+api_@types+node@24.2.0_typescript@5.8.3/node_modules/@directus/api/dist/permissions/modules/process-payload/process-payload.js:85:60 at Array.map (<anonymous>) at file:///directus/node_modules/.pnpm/@directus+api@file+api_@types+node@24.2.0_typescript@5.8.3/node_modules/@directus/api/dist/permissions/modules/process-payload/process-payload.js:85:43 at Array.map (<anonymous>) at processPayload (file:///directus/node_modules/.pnpm/@directus+api@file+api_@types+node@24.2.0_typescript@5.8.3/node_modules/@directus/api/dist/permissions/modules/process-payload/process-payload.js:85:14) at ItemsService.updateMany (file:///directus/node_modules/.pnpm/@directus+api@file+api_@types+node@24.2.0_typescript@5.8.3/node_modules/@directus/api/dist/services/items.js:564:21) at process.processTicksAndRejections (node:internal/process/task_queues:105:5) at async ItemsService.updateOne (file:///directus/node_modules/.pnpm/@directus+api@file+api_@types+node@24.2.0_typescript@5.8.3/node_modules/@directus/api/dist/services/items.js:468:9) at async file:///directus/node_modules/.pnpm/@directus+api@file+api_@types+node@24.2.0_typescript@5.8.3/node_modules/@directus/api/dist/controllers/items.js:139:31 "name": "DirectusError", "extensions": { "field": "email", "path": [], "type": "required" }, "code": "FAILED_VALIDATION", "status": 400 } [00:43:03] PATCH /items/musicians/a52911a9-ab97-4f5a-8190-1a25ba735f03 400 20ms

If I query the database for validations on that email field, there are none.

2

I figured this out! I used the API to look at the fields in the collection and saw this validation for a related field in the collection:

"validation": {
                    "_and": [
                        {
                            "email": {
                                "_submitted": true
                            }
                        }
                    ]
                }

That led me to a validation on a related field that apparently was requiring the email to be submitted, which makes no sense. Nonetheless I am back in business.