> 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-release-notes/6.13/addressed-issues.md).

# Addressed Issues

These issues are fixed in the Cortex XSOAR 6.13 release.

| Category            | Description                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |
| ------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| APIs                | <ul><li>When running the Core REST API command to delete file entries, an error was generated.</li><li>An invalid API master key caused an error to appear in logs and a few hosts to randomly disconnect.</li></ul>                                                                                                                                                                                                                                                         |
| General             | <ul><li>After upgrading from Cortex XSOAR 6.10 to 6.12, the Settings page did not load and an error appeared.</li><li>The Cortex XSOAR server restarted unexpectedly.</li><li>A mandatory markdown field could not be updated or saved if its initial value was empty.</li></ul>                                                                                                                                                                                             |
| Incidents           | <ul><li>Certain authenticated but unauthorized users could access restricted incident data through a specific command.</li><li>Users creating an incident were able to access it even though their role was not assigned to it.</li><li>When searching for incidents using the Triage SLA field, inaccurate results were returned.</li><li>In some cases, preprocess rules were not editable or able to be reordered.</li></ul>                                              |
| Integrations        | <ul><li>When configuring long running integrations, Cortex XSOAR did not fetch 3rd party credentials, and populate them in the configured instance.</li><li><p>When creating an integration instance that fetches credentials, if the integration instance failed while fetching the credentials, the following error was displayed when trying to access the Credentials tab:</p><p><code>"Couldn't transform result content to credentials sets (66)"</code></p></li></ul> |
| Jobs                | When running a nightly job in Cortex XSOAR, the job ran twice when daylight saving time began and when daylight savings time ended.                                                                                                                                                                                                                                                                                                                                          |
| Multi-tenant        | <ul><li>Users deleted in the Main account were not deleted correctly in one of the child tenants.</li><li>Using propagation labels to remove content from tenants, sometimes did not completely remove the content.</li><li>Child investigation roles were not updated correctly.</li></ul>                                                                                                                                                                                  |
| Playbooks           | <ul><li>Files generated when running playbooks in edit mode could not be accessed or downloaded.</li><li>When creating a playbook and using a variable such as <code>${incident.name}</code> in the <strong>Message body</strong> field of a Conditional Ask task, the variable was not resolved and the variable name was displayed in the incident.</li></ul>                                                                                                              |
| Remote Repositories | When trying to push content from dev to prod and there was a conflict, such as an incident field of a different type, there was no content installation conflict message displayed, and the existing content on prod remained.                                                                                                                                                                                                                                               |
| Reports             | <ul><li>The reference line created in the Widget Builder in the graph section did not appear when generating a report.</li><li>When exporting CSV reports from Cortex XSOAR and opening them in Excel, the Hebrew text was not automatically readable.</li><li>When generating a report of type <strong>Line</strong>, the chart was generated in UTC, regardless of the <strong>reports.time.zone</strong> setting.</li></ul>                                               |
| Scripts             | When running an incident post-processing script to stop a timer, the built-in incident closure process caused the post-processing script to execute 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 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/xsoar-6-release-notes/6.13/addressed-issues.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.