> 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-cloud-posture-management/cases-and-issues/investigation-and-response/build-xql-queries/manage-scheduled-queries.md).

# Manage scheduled queries

Learn how to manage your scheduled and recurring queries.

The **Scheduled Queries** page displays information about your scheduled and recurring queries. From this page, you can edit scheduled query parameters, view previous executions, disable, and remove scheduled queries. Right-click a query to see the available options.

<details>

<summary>View executed queries</summary>

1. Select **Investigation & Response** → **Search** → **Scheduled Queries**.
2. Locate the scheduled query for which you want to view previous executions.

   If necessary, use the **Filter** to reduce the number of queries returned.
3. Right-click anywhere in the query row, and select **Show executed queries**.

   Cortex Cloud filters the queries on the **Query Center**.

</details>

<details>

<summary>Edit the query frequency</summary>

1. Select **Investigation & Response** → **Search** → **Scheduled Queries**.
2. Locate the scheduled query that you want to edit.

   If necessary, use the **Filter** to reduce the number of queries returned.
3. Right-click anywhere in the query row and then select **Edit**.
4. Adjust the schedule settings, and then click **OK**.

</details>


---

# 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-cloud-posture-management/cases-and-issues/investigation-and-response/build-xql-queries/manage-scheduled-queries.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.