---
schema_version: "1"
id: 410fc3c515a58eeced47e623b419e7f8c4b59c4e9ccdae6e102a4165a00404a7
title: Troubleshooting the Validation Module
collection: mulesoft
version: current
locale: en-us
portal_url: https://docs.salesforce.com/mulesoft/current/en-us/validation-connector/1.4/validation-module-troubleshooting.md
canonical_url: https://docs.mulesoft.com/validation-connector/1.4/validation-module-troubleshooting
source_site: docs.mulesoft.com
content_type: documentation
content_hash: 51abf5b1452e08d636bf66f4be1418b1b69b3931828cfaeaef87267f000d9a8f
description: MuleSoft Documentation Site
release: "1.4"
latest: false
---
---
product: Validation Module
version: 1.4
---

# Troubleshooting the Validation Module

> For the full documentation index, see: https://docs.mulesoft.com/llms.txt

To troubleshoot the Validation module, become familiar with the information about enabling verbose
logging and interpreting commonly thrown messages.

## Enable Verbose Logging

To get a better understanding of why an application’s interaction with the Validation module is
failing, temporarily enable verbose logging for the module.

Remember to always disable the enhanced verbosity after troubleshooting, because it affects your
Mule application performance.

To enable verbose logging in the configuration file:

1.  Access Anypoint Studio and navigate to the **Package Explorer** view.

2.  Open your application’s project name.

3.  Open the `src/main/resources` path folder.

4.  Open the `log4j2.xml` file inside the folder.

5.  Add an `<AsyncLogger>` tag inside the `<Loggers>` tag:

    ```xml
    			<Loggers>
    				...
    				<AsyncLogger name="org.mule.extension.validation" level="DEBUG"/>
    				...
    			</Loggers>
    ```

6.  Save your application changes.

7.  Click the project name in **Package Explorer** and then click **Run** > **Run As** > **Mule
    Application**.

## Understand Common Throws

Here is a list of common throw messages and how to interpret them:

- VALIDATION:BLANK\_STRING

  The provided value is an empty string and the expected value is not.

- VALIDATION:NOT\_BLANK\_STRING

  The provided value is not an empty string and the expected value is.

- VALIDATION:ELAPSED\_TIME

  Too much time has elapsed since the specified start time.

- VALIDATION:NOT\_ELAPSED\_TIME

  Not enough time has elapsed since the specified start time.

- VALIDATION:INVALID\_EMAIL

  The provided value is an invalid email address.

- VALIDATION:EMPTY\_COLLECTION

  The provided value is an empty collection and the expected value is not.

- VALIDATION:NOT\_EMPTY\_COLLECTION

  The provided value is an empty collection and the expected value is not.

- VALIDATION:INVALID\_BOOLEAN

  The provided value does not match the expected boolean value.

- VALIDATION:INVALID\_IP

  The provided value is an invalid IP address.

- VALIDATION:REJECTED\_IP

  The provided value is not valid according to the expecting ranges.

- VALIDATION:NULL

  The value provided is null. Keep in mind that the definition of \`null\` can vary depending on the
  mimeType value. For example, for an \`application/java\` mimeType, \`null\` means a blank pointer.
  However, if the mimeType is \`application/json\`, then the String \`null\` is also a null value.

- VALIDATION:NOT\_NULL

  The value provided is not null. Keep in mind that the definition of \`null\` can vary depending on
  the mimeType value. For example, for an \`application/java\` mimeType, \`null\` means a blank
  pointer. However, if the mimeType is \`application/json\`, then the String \`null\` is also a null
  value.

- VALIDATION:INVALID\_NUMBER

  The provided value does not satisfy either the number type or the minimum or maximum expected
  values.

- VALIDATION:INVALID\_TIME

  The provided value is an invalid time for the pattern used to parse it. If no pattern is provided,
  then the locale's default is used.

- VALIDATION:INVALID\_URL

  The provided value is an invalid URL.

- VALIDATION:MISMATCH

  The provided value does not match the regular expression.

- VALIDATION:INVALID\_SIZE

  The provided value is not between the specified inclusive boundaries.

- VALIDATION:MULTIPLE

  Summarizes all the found errors in a list of nested validation operations.

## See Also

- [Salesforce Help](https://help.salesforce.com)

- [Validation Module Reference](https://docs.mulesoft.com/validation-connector/1.4/validation-documentation)