MuleSoft · Validation Module
VALIDATION:INVALID_NUMBER
Short answer
VALIDATION:INVALID_NUMBER is thrown by the Validation module's Is number operation when the value is not a valid number for the configured settings. 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:INVALID_NUMBER02Likely causes
- The Is number operation failed: the value is not a valid number for the configured settings.
- If a validation fails, an error is thrown. Its type is always a child of
VALIDATION:VALIDATION.
03How to fix it
- Log the value the validator's expression resolves to, and compare it with what the validator expects.
- Check the value and the number settings on 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:INVALID_NUMBER, for example to return a 400 response.
04Official documentation
→Related errors
- VALIDATION:INVALID_SIZEVALIDATION:INVALID_SIZE is thrown by the Validation module's Validate size operation when the size of the value is outside the configured range. Check the value passed to the validator, and handle the error type if invalid input is something the flow should answer cleanly.
- VALIDATION:MISMATCHVALIDATION:MISMATCH is thrown by the Validation module's Matches regex operation when the value does not match the regular expression. 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