MuleSoft · Validation Module

VALIDATION:EMPTY_COLLECTION

Short answer

VALIDATION:EMPTY_COLLECTION is thrown by the Validation module's Is not empty collection operation when the collection is empty. 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

MuleSoft error
Error type: VALIDATION:EMPTY_COLLECTION

02Likely causes

  • The Is not empty collection operation failed: the collection is empty.
  • If a validation fails, an error is thrown. Its type is always a child of VALIDATION:VALIDATION.

03How to fix it

  1. Log the value the validator's expression resolves to, and compare it with what the validator expects.
  2. Check the query or transformation that builds the collection, and decide whether an empty result is an error.
  3. Set the validator's Message parameter to say what was wrong, so the error description is useful to the caller.
  4. Handle the failure with an error handler of type VALIDATION:EMPTY_COLLECTION, for example to return a 400 response.

04Official documentation

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

The iPaaS Brief

Subscribe to The iPaaS Brief.

The iPaaS newsletter for the people who run integrations. From iPaaS Group.

Free. You finish on theipaasbrief.com and confirm by email.