MuleSoft · Validation Module
VALIDATION:NOT_NULL
Short answer
VALIDATION:NOT_NULL is thrown by the Validation module's Is null operation when a value was expected to be null but is not. Check the value passed to the validator, and handle the error type if invalid input is something the flow should answer cleanly.
VerifiedLast verified
01Error text
Error type: VALIDATION:NOT_NULL02Likely causes
- The Is null operation failed: a value was expected to be null but is not.
- If a validation fails, an error is thrown. Its type is always a child of
VALIDATION:VALIDATION. - The definition of
nullcan vary depending on the MIME type of the value.
03How to fix it
- Log the value the validator's expression resolves to, and compare it with what the validator expects.
- Check why the value is set when the flow expects it to be absent.
- Set the validator's Message parameter to say what was wrong, so the error description is useful to the caller.
- Handle the failure with an error handler of type
VALIDATION:NOT_NULL, for example to return a 400 response.
04Official documentation
→Related errors
- VALIDATION:NULLVALIDATION:NULL is thrown by the Validation module's Is not null operation when the value is null. Check the value passed to the validator, and handle the error type if invalid input is something the flow should answer cleanly.
- VALIDATION:NOT_EMPTY_COLLECTIONVALIDATION:NOT_EMPTY_COLLECTION is thrown by the Validation module's Is empty collection operation when the collection was expected to be empty but has elements. Check the value passed to the validator, and handle the error type if invalid input is something the flow should answer cleanly.
Test every fix in a non-production environment before you apply it to production. See how entries are verified.
More for MuleSoft work:Open MuleSoft jobsMuleSoft rates and salariesHire a senior MuleSoft developer