> 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-expander-rn/hotfix-releases/july-2024.md).

# July 2024

The tables below lists the bug fixes and enhancements in July 2024 hotfix releases.

## Hotfix Release - July 28, 2024

The table below lists the bug fixes and enhancements in the July 28, 2024 hotfix release.

| Issue or Enhancement | Issue Type  | Description                                                                                                                                                  |
| -------------------- | ----------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| XPSUPPORT-2918       | Bug Fix     | Corrected a typo in the CERTIFICATE SUBJECT ALTERNATIVE NAME(S) column heading.                                                                              |
| XPSUPPORT-2713       | Bug Fix     | Fixed a bug that caused some alerts to have an incorrect alert resolution status.                                                                            |
| EXPANDR-10157        | Improvement | The attack surface test fields will be included in the Get All Services and Get Service Details API responses, even when attack surface testing is disabled. |
| EXPANDR-10012        | Bug Fix     | Fixed a bug where the Total Active Critical/High Alerts on All Threats link on the Threat Response Center applied the severity filter twice.                 |


---

# 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/cortex-xpanse-expander-rn/hotfix-releases/july-2024.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.