> 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.12/configure-cortex-xsoar/customize-and-configure-cortex-xsoar/reports/troubleshoot-reports.md).

# Troubleshoot Reports

Follow the procedures below to troubleshoot reports.

* [Generate a JSON File](#generate-a-json-file)
* [Troubleshoot Incorrect Dates](#troubleshoot-incorrect-dates)
* [Troubleshoot Overlapping Text and Extra Pages (PDF)](#troubleshoot-overlapping-text-and-extra-pages-pdf)
* [Troubleshoot Script Timeout for Reports](#troubleshoot-script-timeout-for-reports)

### Generate a JSON File

By default, when you generate a report the JSON file is not retained. This JSON file is needed to troubleshoot report issues.

1. Select Settings → About → **Troubleshooting** → **Add Server Configuration**.
2. Add the following key and value.

   | Key                      | Value       |
   | ------------------------ | ----------- |
   | **`report.remove.data`** | **`false`** |
3. Save the configuration.
4. Generate the report.
5. Download the JSON file from `/var/lib/demisto/temp/`.
6. Go to Settings → About → **Troubleshooting** and delete the server configuration you created.

### Troubleshoot Incorrect Dates

When creating a PDF for incidents that includes open/close dates, SLA, etc. and those dates are incorrect use the following procedure.

1. Select Settings → About → **Troubleshooting** → **Add Server Configuration**.
2. Add the following key and value.

   | Key                       | Value                                 |
   | ------------------------- | ------------------------------------- |
   | **`reports.time.format`** | **`Thursday, 02-Jan-2006 15:05 GMT`** |
3. Save the configuration.

### Troubleshoot Overlapping Text and Extra Pages (PDF)

When creating or exporting a PDF of a report with long tables and large amounts of text, some text might overlap. You can avoid this by adding a page break after the long text.

{% hint style="info" %}

### Note

Adding page breaks manually might result in extra blank pages in the PDF.
{% endhint %}

Use the following procedure.

1. In the report, after any widget that can potentially have a lot of text, click **Add Widget**.
2. In the **Widgets Library** section, search for **Page Break Widget** and click **Add**.
3. Repeat for other widgets.
4. Click **Save**.

### Troubleshoot Script Timeout for Reports

If you generate a report that runs a script and that report or the section that has the script is blank/empty, you should increase the script timeout value. Automations (scripts) have a default timeout value of 3 minutes.

1. Go to Settings → About → **Troubleshooting**.
2. Click **Add Server Configuration**.
3. Add the following key and value.

   | Key                  | Value    |
   | -------------------- | -------- |
   | **`script.timeout`** | **`10`** |
4. Generate the report.


---

# 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-administrator-guide/6.12/configure-cortex-xsoar/customize-and-configure-cortex-xsoar/reports/troubleshoot-reports.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.