MuleSoft · Validation Module

VALIDATION:NOT_EMPTY_COLLECTION

Short answer

VALIDATION: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.

VerifiedLast verified

01Error text

MuleSoft error
Error type: VALIDATION:NOT_EMPTY_COLLECTION

02Likely causes

  • The Is empty collection operation failed: the collection was expected to be empty but has elements.
  • 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 why the collection has elements when the flow expects none.
  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:NOT_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.