> For the complete documentation index, see [llms.txt](https://docs.commercelayer.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.commercelayer.io/core-api-reference/resource_errors.md).

# Resource errors

The resource error object and the allowed CRUD operations on the related resource endpoint

Resource errors are generated anytime an operation on a resource fails to let you inspect the related errors by looking at the `code` and `message` attributes. To do that, just fetch the resource and [include](/core/including-associations.md) `resource_errors` as an association (you must use [integration](/core/api-credentials.md#integration) API credentials).

{% hint style="info" %}
At the moment resource errors are available for [orders](/core-api-reference/orders.md#order-errors), [returns](/core-api-reference/returns.md#refunding-from-a-return), and resources involving transactions in general (in the future the feature will be extended to other resources).
{% endhint %}

## Orders

Most of the errors generated by the management of your orders are included in the associated resource errors array. Among them:

* Errors occurred during the attempt to place an order (both synchronously and [asynchronously](/core-api-reference/orders.md#asynchronous-order-placement)).
* Errors coming from [external validations](/core-api-reference/orders.md#order-validation).
* Errors due to failed [subscription](/core-api-reference/orders.md#automatic-subscriptions-generation) occurrences.

For each order, the latest **10** errors are stored. Once the order is approved, the associated errors list is emptied and the errors count is reset to zero.

{% hint style="info" %}
This is an **immutable API**, meaning that create, update, and delete operations are not allowed on this endpoint. You can only fetch a list of resource errors or a single resource error object.
{% endhint %}


---

# 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://docs.commercelayer.io/core-api-reference/resource_errors.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.