# Debugging

Here's a general list of troubleshooting steps if you're getting errors. The log files are VERY important since Lucee's error doesn't always contain the information you need. You must crack open your Lucee logs to get the actual error out.

* Look in the `out` and `err` logs for information. These are usually found in the servlet container's log directory. For instance, if you're using Tomcat, look in Tomcat's `log` directory. Messages are often logged there that never make it up to the CFML engine.
* Always scroll to the bottom of Java stack traces to look for a **caused by** section, which is the original error.


---

# 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://ortuspdf.ortusbooks.com/essentials/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.