> 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/cortex-xpanse/active-response/troubleshoot-active-response.md).

# Troubleshoot Active Response

To fix a playbook error for an alert, restart the playbook.

{% hint style="warning" %}

### Caution

When you restart the playbook, any data collected by the previous playbook execution may be lost.
{% endhint %}

1. On the **Incident Response** → **Incidents** page, select the incident that has an alert with a playbook error.
2. In the details pane, select the **Overview** tab .
3. Scroll to the alert with the alert with the playbook error, and click **Restart Playbook**.

If restarting the playbook does not fix the error, reach out to a member of the Customer Success Team.


---

# 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://cortex-docs.paloaltonetworks.com/cortex-xpanse/active-response/troubleshoot-active-response.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.