> For the complete documentation index, see [llms.txt](https://docs.devolutions.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.devolutions.net/rdm/es/knowledge-base/how-to-articles/send-an-error-report.md).

# Enviar un informe de error

Envíe un informe de error desde Remote Desktop Manager al servicio de atención al cliente con sus datos de contacto para ayudar a reproducir el problema.

Se crea un informe de error cuando se produce un error de la aplicación en Remote Desktop Manager. Puede enviar ese informe de error a nuestro equipo de atención al cliente para ayudar a reproducir el problema más fácilmente.

{% hint style="success" %}
Cuando envíe su informe de error, asegúrese de incluir tantos detalles como sea posible en la sección del mensaje para garantizar que nuestro equipo de atención al cliente reproduzca el problema con facilidad.
{% endhint %}

### Enviar un informe de error

Cuando aparezca un cuadro de diálogo de error en Remote Desktop Manager, siga estos pasos para enviarlo al equipo de atención al cliente.

1. Pulse el botón ***Send Error Report***.
2. Rellene su información de contacto junto con una explicación detallada del problema y pulse ***OK***.


---

# 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.devolutions.net/rdm/es/knowledge-base/how-to-articles/send-an-error-report.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.
