> 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/all-schedules.md).

# All Schedules

This tab lists every piece of scheduled work: recurring schedules and queued one-time jobs. Use it to find work whose last run failed, see what is due next, keep platform collection running, and pause, resume or change a schedule.

Open it from **Operations** → **Schedules** → **All schedules** in the sidebar.

{% hint style="warning" %}
You need a role that can view jobs. Scheduling, editing, pausing, resuming and archiving need a role that can configure jobs. Opening execution history needs a role that can view job executions.
{% endhint %}

<figure><img src="https://1912836914-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9vAxMuDrkUkB4OXlH9CL%2Fuploads%2Fnr67LyiGJywSKc1YGiPt%2Fv2-sched-list.png?alt=media&amp;token=e2a4b19c-1553-4b5f-ae54-f05a132d5ebb" alt="All schedules tab with the platform collection strip, filters, summary tiles and the schedule table"><figcaption></figcaption></figure>

## Platform Collection

The **Platform collection** strip shows the inventory syncs of your connected platforms (Anypoint, Azure and AWS), each with a status dot, and how often they run. Hover over a platform to see its timing and last run. Click **Manage** to open the **Platform collection** drawer.

<figure><img src="https://1912836914-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9vAxMuDrkUkB4OXlH9CL%2Fuploads%2F4kTQPbNEUDwSDwz7OpoQ%2Fv2-sched-collection.png?alt=media&amp;token=7ab4ce3e-fb00-462b-b851-c387a617ecd9" alt="Platform collection drawer with a platform scan schedule and the Anypoint, Azure Integration Services and AWS syncs"><figcaption></figcaption></figure>

The drawer lists:

* **Platform scan schedules**: one per organization and collection scope for AWS, MuleSoft or Azure Integration Services. Each shows its organization, how many asset types and regions or environments it covers, its timing and cadence exceptions, and how many of its schedules are active. Click its name or **Edit schedule** to change it. See **Schedule a Platform Scan** below.
* **Platform syncs**: the workspace-wide inventory sync of each platform, with its timing, next run, last run and state (**Scheduled**, **Paused** or **Not scheduled**). **Sync now** queues a sync immediately. **Edit schedule** (or **Schedule** when there is none) sets its recurring interval; confirm with **Save schedule** or **Create schedule**. A platform that is not connected yet shows a link to Setup.

**Schedule platform scan** at the top of the drawer, and at the top of the tab, starts a new platform scan schedule.

## Filters and Summary Tiles

| Filter            | Description                                                                                                              |
| ----------------- | ------------------------------------------------------------------------------------------------------------------------ |
| **Organizations** | The organizations the work belongs to.                                                                                   |
| **Environments**  | The environments the work runs in.                                                                                       |
| **Status**        | **Active**, **Disabled**, **Needs attention**, **Paused**, **Completed one-time** or **Archived**.                       |
| **Last run**      | The result of the last run, for example **Completed**, **Failed** or **Stopped**.                                        |
| **Frequency**     | Under **Filters**: **Recurring** or **One-time**.                                                                        |
| **Job types**     | Under **Filters**: the kind of work, for example a platform analysis, a repository scan or an AI evidence investigation. |

**Saved filters** and **Save filters** keep a combination of filters for later.

| Tile                 | Shows                                                     |
| -------------------- | --------------------------------------------------------- |
| **Needs attention**  | Work whose last execution failed, stopped or was blocked. |
| **Active work**      | Enabled schedules and queued one-time jobs.               |
| **Paused schedules** | Recurring work that will not run until resumed.           |

Click a tile to filter the table.

## Schedule Table

The table lists the newest enabled work first, 10 per page, and follows the filters above. Switch between **Active** and **Disabled** work above the table. **Search schedules** finds a schedule, **Refresh** reloads the table, **Columns** shows or hides columns and **Export this page** downloads the rows on the current page.

| Column        | Description                                                                                                                                                              |
| ------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| **Schedule**  | The schedule name and its organization and environment. Click the name to open its details.                                                                              |
| **Frequency** | The timing in words, the cron expression of a recurring schedule, and the asset type when there is one.                                                                  |
| **Last run**  | The status of the last run, for example **Completed** or **Failed**, and how long ago it ran.                                                                            |
| **Next run**  | When active work runs next (**Awaiting scheduler** until it is planned), or **Paused**, **Archived**, **Finished / disabled** or **On-demand & change-triggered scans**. |
| **Actions**   | The row actions below. Actions that do not fit open from **More actions**.                                                                                               |

| Action                | What it does                                                             |
| --------------------- | ------------------------------------------------------------------------ |
| **Inspect run**       | Opens the schedule's details and the output of its last execution.       |
| **Execution history** | Opens the execution history of this schedule only.                       |
| **Edit schedule**     | Changes the timing of a recurring schedule.                              |
| **Pause schedule**    | Stops future runs until you resume. A running execution is not affected. |
| **Resume schedule**   | Lets the scheduler pick up paused recurring work again.                  |
| **Run again**         | Queues a completed one-time job to run again.                            |

Pausing, resuming and running again ask you to confirm first.

## Schedule Details

Click a schedule's name or **Inspect run** to open its details:

| Field                        | Description                                        |
| ---------------------------- | -------------------------------------------------- |
| **Scope**                    | The organization and environments the work covers. |
| **Schedule**                 | The timing in words, with its time zone.           |
| **Cron (UTC)**               | The cron expression of a recurring schedule.       |
| **Status**                   | The schedule status, for example **Active**.       |
| **Last execution**           | The status of the last run.                        |
| **Last completed / updated** | When the last run finished or last changed.        |
| **Next scheduled run**       | When the work runs next.                           |

**Last execution evidence** shows the recorded scheduler output for this job; **Refresh** reloads it. For report schedules, the drawer also lets you change who receives the report.

**Archive schedule** stops future runs and moves the schedule to **Archived**. The record is kept.

## Schedule a Platform Scan

Use a platform scan schedule to collect and assess all the asset types of a connected AWS, MuleSoft or Azure Integration Services organization with one cadence.

1. Click **Schedule platform scan**.
2. Under **Choose the collection scope**, choose the **Organization / connection** and enter a **Schedule name**.
3. Choose the regions or environments to cover, for example **Regions** for AWS.
4. Under **When should this work run?**, choose **One time** or **Recurring**. For **Recurring**, choose the interval and whether to enable the schedule after saving.
5. Under **Asset types and exceptions**, clear the asset types you do not want to collect. For a recurring schedule, click **Set exception** next to an asset type's timing to give it its own cadence; **Use default** removes the exception.
6. For **One time**, click **Run&#x20;*****N*****&#x20;scans now** to queue the scans immediately.
7. For **Recurring**, click **Review schedule changes**, check **Review what will change**, then click **Save&#x20;*****N*****&#x20;schedules**. **Back to settings** returns to the form.

<figure><img src="https://1912836914-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9vAxMuDrkUkB4OXlH9CL%2Fuploads%2FY1bzrrjzkhAcNuDHzxKv%2Fv2-sched-platform-scan.png?alt=media&amp;token=98f8dbdf-9274-4b58-8308-f56b6187a5f9" alt="Schedule a platform scan drawer with collection scope, recurring timing and asset types with Set exception links"><figcaption></figcaption></figure>

| Field                          | Description                                                                                                                                                                                                               |
| ------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Organization / connection**  | The connected organization and its platform. It decides which platform connection is used; credentials are never copied into schedules. It cannot be changed when you edit an existing plan.                              |
| **Schedule name**              | The plan name, up to 80 characters.                                                                                                                                                                                       |
| **Regions** / environments     | The AWS regions, or the environments of other platforms, to collect from. For MuleSoft, Exchange assets are collected once for the business group, while Runtime Manager and API instances use each selected environment. |
| **One time** / **Recurring**   | Run the scans once, or on a recurring interval. All times use UTC.                                                                                                                                                        |
| **Enable platform schedule**   | For a recurring plan: **Enable after saving**, or **Save paused**.                                                                                                                                                        |
| **Asset types and exceptions** | The asset types included. New asset types or environments are added when you edit and save the plan.                                                                                                                      |

{% hint style="info" %}
A platform scan schedule changes only timing and collection scope. Eligibility, quality profiles, source retention, AI review profiles and budgets keep their settings. Existing individual schedules in the same scope are shown in the preview before they are included.
{% endhint %}

{% hint style="warning" %}
**No connected platform is available** means no organization is connected yet, or you cannot edit its licensed asset types. Connect an organization first.
{% endhint %}

## Edit a Schedule's Timing

1. Click **Edit schedule** on a recurring schedule's row (under **More actions** when needed).
2. Under **When should this work run?**, choose a preset interval, or **Custom schedule** to build your own with the **Minutes**, **Hourly**, **Daily**, **Weekly**, **Monthly** or **Custom** tabs. The builder shows the schedule in words and as a cron expression.
3. Click **Submit**. **Back to all schedules** returns to the list without saving.

<figure><img src="https://1912836914-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9vAxMuDrkUkB4OXlH9CL%2Fuploads%2FJlK7bh1oYRXmNDPvhfhw%2Fv2-sched-edit.png?alt=media&amp;token=ab4ebf91-6da9-4046-ad1b-5176751f44a9" alt="Edit schedule page with the recurring interval and the Submit button"><figcaption></figcaption></figure>

The preset intervals are **Every 15 minutes**, **Every hour**, **Every 6 hours**, **Every 12 hours**, **Daily at midnight**, **Daily at 02:00**, **Weekdays at 09:00**, **Weekly on Monday at 02:00** and **Monthly on day 1 at 08:00**.

### Cron Expressions

Schedules use Quartz cron expressions with seven fields: seconds, minutes, hours, day of month, month, day of week and year. Use `?` in either the day-of-month or the day-of-week field. For example, **Daily at 02:00** (UTC) is:

```
0 0 2 1/1 * ? *
```

and **Weekdays at 09:00** is `0 0 9 ? * MON-FRI *`.

## Next Steps

* [Execution History](https://knowledgebase.autorabit.com/product-guides/integral-zone/iz-suite/operations/schedules/execution-history.md): inspect the runs a schedule produced.
* [Quality Profiles](https://knowledgebase.autorabit.com/product-guides/integral-zone/iz-suite/operations/quality-control/quality-profiles.md): set the rules that scheduled assessments use.
* [Schedules](https://knowledgebase.autorabit.com/product-guides/integral-zone/iz-suite/operations/schedules.md): return to the Schedules 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/all-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.
