> 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-legacy/iz-core/schedules/job-schedules.md).

# Job Schedules

Job Schedules lists all the schedules created in the system

{% hint style="warning" %}

* Job Schedules can be either of the following types
* **`One Time`** - Job will only be executed once
* **`Regular Interval`** - Jobs will run based on the configured schedule
  {% endhint %}

### Schedules

1. Navigate to **`Schedules`** -> **`Schedules`**

<figure><img src="https://1912836914-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9vAxMuDrkUkB4OXlH9CL%2Fuploads%2FBKk8OmYFmGnNpBIpCXVZ%2Fjob-schedules.png?alt=media&amp;token=6ad2e0f3-0deb-413d-b151-63e4592e14ef" alt=""><figcaption></figcaption></figure>

2. **`Status`** column indicates the Job status. A **`One Time`** job will be automatically disabled once the execution is complete
3. Click on **`Disable Job`** to disable any active job instances
4. Click on **`View Executions`** to view the list of executions for the configured schedule

<figure><img src="https://1912836914-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9vAxMuDrkUkB4OXlH9CL%2Fuploads%2F7gBziJl0jNvBA3E3wPSC%2Fjob-executions.png?alt=media&amp;token=b0ef32b4-4298-4a61-ad7e-db379bba7cf4" alt=""><figcaption></figcaption></figure>

### How Schedules Are Executed

1. The IZ Server evaluates every enabled schedule and records when it fired last and when it is due next.
2. When a schedule is due, the server queues it. Any running agent that supports the schedule's job type picks it up and creates the job executions for the selected organizations and environments.
3. Pending job executions are allocated to free agent workers every 10 seconds. In a multi-tenant installation, allocation is fair across tenants.
4. If no agent supporting the job type is running, the schedule stays queued until one starts. Check **`Global Settings`** -> **`Agents`** when schedules do not run.

### See Also

* [Job Executions](https://knowledgebase.autorabit.com/product-guides/integral-zone/iz-suite-legacy/iz-core/schedules/job-executions.md)


---

# 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-legacy/iz-core/schedules/job-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.
