MuleSoft · Validation Module
VALIDATION:INVALID_TIME
Short answer
VALIDATION:INVALID_TIME is thrown by the Validation module's Is time operation when the value is not a valid time for the configured pattern. 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_TIME02Likely causes
- The Is time operation failed: the value is not a valid time for the configured pattern.
- 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 against the pattern and locale set 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_TIME, for example to return a 400 response.
04Official documentation
→Related errors
- 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.
- Cannot coerce String to DateThis DataWeave error means a String could not be converted to a Date because the text is not a valid date for the format and parsing mode in use. Correct the input value, or pick a parsing mode that fits how strict you need to be.
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