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

# Debugging

It is possible to enable more log messages from the proxy by enabling the `DEBUG` environment variable, this can help in getting more information if something does not work as expected.

Another tool that is very helpful when running BullMQ is a dashboard such as [Taskforce.sh](https://taskforce.sh). With this tool it is possible to see all the queues that are available in a Redis™ instance, as well as all the jobs in the different states. This allows to examine the jobs that completed, or maybe more importantly the ones that have failed, so that they can be analyzed and when the root cause resolved optionally retried. There are many more features provided by the dashboard, just give it a try to see what it can do for you.


---

# 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 dynamically by asking a question.

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

```
GET https://docs.bullmq.net/http-api/debugging.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.