> 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-runtime-security/cases-and-issues/investigation-and-response/build-xql-queries/manage-scheduled-queries/scheduled-queries-reference-information.md).
# Scheduled Queries reference information
The table below lists the common fields in the **Scheduled Queries** page.
{% hint style="info" %}
### Note
Certain fields are exposed and hidden by default. An asterisk (\*) is beside every field that is exposed by default.
{% endhint %}
Scheduled Queries table
| Field | Description |
| --------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **BQL** | Whether the query was created by the native search.
Native search has been deprecated, this field allows you to view data for queries performed before deprecation.
|
| **ISSUED BY** | User who ran or scheduled the query. |
| **MITRE ATT\&CK TACTIC** | MITRE ATT\&CK tactics tagged in the scheduled query. |
| **MITRE ATT\&CK TECHNIQUE** | MITRE ATT\&CK techniques tagged in the scheduled query. |
| **NEXT EXECUTION** | For queries that are scheduled to run at a specific frequency, this displays the next execution time.
For queries that were scheduled to run at a specific time and date, this field will show None.
|
| **PUBLIC API** | Whether the source executing the query was an XQL query API. |
| **QUERY DESCRIPTION** | Query parameters used to run the query. |
| **QUERY ID** | Unique identifier of the query. |
| **QUERY NAME** | - For saved queries, the Query Name identifies the query specified by the administrator.
- For scheduled queries, the Query Name identifies the auto-generated name of the parent query. Scheduled queries also display an icon to the left of the name to indicate that the query is recurring.
|
| **QUERY SYNTAX** | The exact syntax used to write the query. |
| **SCHEDULE TIME** | Frequency or time at which the query was scheduled to run. |
| **XQL** | Whether the query was created by XQL search. |
---
# 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/cortex-cloud-runtime-security/cases-and-issues/investigation-and-response/build-xql-queries/manage-scheduled-queries/scheduled-queries-reference-information.md?ask=&goal=
```
`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.