> For the complete documentation index, see [llms.txt](https://knowledgebase.autorabit.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://knowledgebase.autorabit.com/product-guides/integral-zone/iz-suite/operations/schedules.md).

# Schedules

**Schedules** shows the work IZ Suite runs on a schedule or once: collecting assets from connected platforms, scanning repositories, syncing connections, checking endpoint health and producing reports. Agents pick up each run, and every run is recorded with its status and log.

Open it from **Operations** → **Schedules** in the sidebar. The tabs at the top switch between the sections below. Each tab appears only when your role can view it.

<figure><img src="https://1912836914-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9vAxMuDrkUkB4OXlH9CL%2Fuploads%2F31aTDM6NfW2Kcy4wjlUq%2Fv2-sched-tabs.png?alt=media&amp;token=fd14f189-bda3-404a-8083-39c5a1a2660e" alt="Schedules header with the All schedules and Execution history tabs"><figcaption></figcaption></figure>

| Tab                                                                                                                                      | What it is for                                                                                                             |
| ---------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------- |
| [All schedules](https://knowledgebase.autorabit.com/product-guides/integral-zone/iz-suite/operations/schedules/all-schedules.md)         | Recurring and one-time work, platform collection and platform scan schedules, and pausing, resuming or editing a schedule. |
| [Execution history](https://knowledgebase.autorabit.com/product-guides/integral-zone/iz-suite/operations/schedules/execution-history.md) | Every run, its status, assigned worker, timing and recorded log.                                                           |

{% hint style="info" %}
A schedule controls when work is queued. The actual start time depends on the agents and capacity available.
{% endhint %}

## Next Steps

* [All Schedules](https://knowledgebase.autorabit.com/product-guides/integral-zone/iz-suite/operations/schedules/all-schedules.md): schedule a platform scan or change a schedule's timing.
* [Execution History](https://knowledgebase.autorabit.com/product-guides/integral-zone/iz-suite/operations/schedules/execution-history.md): find the run that needs attention.
* [Operations](https://knowledgebase.autorabit.com/product-guides/integral-zone/iz-suite/operations.md): return to the Operations overview.


---

# 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://knowledgebase.autorabit.com/product-guides/integral-zone/iz-suite/operations/schedules.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.
