> For the complete documentation index, see [llms.txt](https://coldbox-validation.ortusbooks.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://coldbox-validation.ortusbooks.com/v3.x-1/overview/validating-constraints/validating-with-failures.md).

# Validating With Failures

In **cbValidation** 1.5 we introduced the `validateOrFail()` function.  This function works in similar manner to the `validate()` method, but instead of giving you the results object, it throws an exception of type `ValidationException`.

| Incoming Target | Validation Fails | Result                                                                              |
| --------------- | ---------------- | ----------------------------------------------------------------------------------- |
| Object          | false            | Returns the same object                                                             |
| Object          | true             | Throws `ValidationException`                                                        |
| Struct          | false            | Returns the structure with ONLY the fields that were validated from the constraints |
| Struct          | true             | Throws `ValidationException`                                                        |

## Exception Extended Info

So your validation fails, where are the results? In the exception structure under the `extendedInfo` key.  We store the validation results as JSON in the extended info and then you can use them for display purposes:

```javascript
try{
    validateOrFail( target );
    service.save( target );
} catch( ValidationException e  ){
    return {
        "error" : true,
        "validationErrors" : deserializeJSON( e.extendedInfo )
    };
}
```

 


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://coldbox-validation.ortusbooks.com/v3.x-1/overview/validating-constraints/validating-with-failures.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.