> 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/release-notes-xsoar-8.16-saas/cortex-xsoar-release-information.md).

# Cortex XSOAR Release Information

Cortex XSOAR combines security orchestration, incident management, and interactive investigation into a seamless experience. The orchestration engine is designed to automate security product tasks and weave in human analyst tasks and workflows.

To view the current operational status of Palo Alto Networks cloud services, including Cortex XSOAR 8 and maintenance releases, see <https://status.paloaltonetworks.com/>. This status page is updated two weeks before any deployment.

We recommend that you subscribe to the status page for service-related announcements.

These Release Notes are relevant for Cortex XSOAR SaaS. To view the Cortex XSOAR On-prem release notes, go to [Cortex XSOAR Release Information](https://docs-cortex.paloaltonetworks.com/r/Cortex-XSOAR/8.12/Cortex-XSOAR-On-prem-Release-Notes/Cortex-XSOAR-Release-Information)


---

# 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 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/release-notes-xsoar-8.16-saas/cortex-xsoar-release-information.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 `automate deployments from our CI pipeline` 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.