MuleSoft · Validation Module
VALIDATION:NULL
Short answer
VALIDATION: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.
VerifiedLast verified
01Error text
Error type: VALIDATION:NULL02Likely causes
- The Is not null operation failed: the value is null.
- 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.
- Fix the upstream step so the value is present, or give it a fallback before the validator.
- 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:NULL, for example to return a 400 response.
04Official documentation
→Related errors
- VALIDATION:NOT_NULLVALIDATION: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.
- VALIDATION:BLANK_STRINGVALIDATION:BLANK_STRING is thrown by the Validation module's Is not blank string operation when the string is blank. Check the value passed to the validator, and handle the error type if invalid input is something the flow should answer cleanly.
- MULE:EXPRESSIONMULE:EXPRESSION means an error occurred while Mule evaluated a DataWeave expression. Find the expression named in the log, check the values it reads for nulls or wrong types, and add a default or a handler.
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