# SMS Debugging/Error Logs

{% hint style="warning" %}
**IMPORTANT: Logging is not available on demo accounts.**

Demo accounts provide only limited access to DEV's product features. You'll need a standard account for full access to logging and more.&#x20;

**Using a demo account?** [Contact us](https://www.plumvoice.com/contact-us/) if interested in upgrading to a standard account.
{% endhint %}

## Debugging

If errors occur with an SMS application, use the error logs to help debug the problem.

To access the error logs, go to the SMS Applications heading and select 'Error Logs'.&#x20;

<div align="left"><img src="/files/-MR5LnwRrpuOc6UIVKwv" alt=""></div>

The log table will populate with any errors that occurred within your application. For more details on a specific error, click the 'View' link on the right side of the table.

![](/files/-M4VUuI4w-AbxBgShm9T)

There, you'll be able to see the error that was generated, including the SMS request, the XML response, and highlighting the line of code that's causing the error (if applicable).

<div align="left"><img src="/files/-M4VUuI6mYhIAZbf7ZeM" alt=""></div>


---

# Agent Instructions: Querying This Documentation

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

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.plumvoice.com/dev/plum-dev-guide/sms-guide/sms-optimization-logs-and-debugging.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
