> For the complete documentation index, see [llms.txt](https://cortex-docs.paloaltonetworks.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cortex-docs.paloaltonetworks.com/xsoar-6-administrator-guide/6.15/customize-cortex-xsoar/customize-and-configure-cortex-xsoar/playbooks/playbook-testing/debugger-troubleshooting.md).

# Debugger Troubleshooting

Troubleshoot the Cortex XSOAR 6.15 playbook debugger.

**User Permissions**

The debugger runs with the permissions of the logged in user. The user must have permissions for both **`PlaybooksRW`** and **`InvestigationRW`** to run the debugger.

**Debugger Worker Pool**

The playbook debugger has a separate worker pool. If you have many users running debugger sessions at the same time, and there are performance issues, you can increase the number of workers. To change the number of workers, go to Settings → About → Troubleshooting → **Server Configuration** and add the server configuration **`workers.count.Debug`**. The default number of workers is 1.

**Terminate Debugger Sessions**

By default, every 24 hours, the system closes any debugger sessions that have been open for more than 180 minutes. You can change the frequency of the automatic terminations and also the length of time a debugger session can remain open. To change the default from 24 hours, go to Settings → About → Troubleshooting → **Server Configuration** and add the server configuration **`clean.playbook.debug.sessions.interval`**. The unit is hours.. To change the maximum time a debugger session can remain open, add the server configuration **`playbook.debug.sessions.duration.max`**. The unit is minutes.

The default admin can close either all debugger sessions or a specific user’s debugger sessions through the API.

* To close all debugger sessions, send a POST request to the endpoint **`/debugsession/remove`**.
* To close only the debugger sessions for a specific user, include the following request parameter in the body of the request **`{"username": "`*****`CHOSEN_USERNAME`*****`"}`**. Note that if no user is specified in the request, all open debugger sessions for all users will be terminated.


---

# 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 following URL with the `ask` and `goal` query parameters:

```
GET https://cortex-docs.paloaltonetworks.com/xsoar-6-administrator-guide/6.15/customize-cortex-xsoar/customize-and-configure-cortex-xsoar/playbooks/playbook-testing/debugger-troubleshooting.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 `build a script that syncs our docs to a CMS` 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.