> For the complete documentation index, see [llms.txt](https://docs.aohwv.dev/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.aohwv.dev/feature-reference/schedule.md).

# Schedule

The Schedule screen gives you a central view of all automated Sync jobs running across your AOH Sync environment — including their cadence, event type, target, and recent run history.

![The Schedule screen showing a "Scheduled Jobs" table with columns for Name, Schedule, Event Type, Target, Status, and Actions (Enable, Disable, Trigger now, Delete), and a "Recent Runs" table below with columns for Run, Job, Status, Started, Finished, Retries, Error, and Actions](/files/jLpEu7IW9kWhsYkhRHsI)

*The Schedule screen shows all active Sync jobs at the top and a live feed of recent runs below. Each job can be triggered on demand or disabled without deleting it.*

{% hint style="info" %}
This is the environment-wide Schedule screen. For the schedule configured on a specific Connector, see [Connector Schedule](/feature-reference/connectors/schedule.md). For the visual Orchestration overview, see [Scheduling & Orchestration](/feature-reference/scheduling-orchestration.md).
{% endhint %}

## Where this data comes from

Scheduled jobs are created directly in AOH Sync — they are not pulled from an external system. The Recent Runs table fills in automatically as jobs execute: AOH Sync writes a run record every time a sync runs, whether it was triggered on schedule or on demand.

## What you can do here

| Action               | What it does                                                                                                                                                                                                            |
| -------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| View scheduled jobs  | See all active Sync jobs with their name, cadence (for example, "Every 5 minutes" or "At 02:00 AM"), event type (such as `sync.delta` for incremental syncs or `sync.full` for full syncs), target, and current status. |
| **Enable**           | Activates a job that was previously disabled so it resumes running on its configured schedule.                                                                                                                          |
| **Disable**          | Pauses a job without deleting it. The job remains visible and can be re-enabled at any time.                                                                                                                            |
| **Trigger now**      | Runs the job immediately, outside of its normal schedule. Useful for testing or forcing a sync after a configuration change.                                                                                            |
| **Delete**           | Permanently removes the scheduled job.                                                                                                                                                                                  |
| **Create a New Job** | Opens the form to define a new scheduled Sync job with a name, cadence, event type, and target.                                                                                                                         |
| View recent runs     | The **Recent Runs** table shows the run identifier, which job it belongs to, its status (for example, complete), the start and finish times, retry count, and any error details.                                        |

## How to use it

{% stepper %}
{% step %}
**Review job health** Check the **Status** column in the Scheduled Jobs table. All jobs should show **Active**. If a job is disabled or missing, investigate whether it was paused intentionally.
{% endstep %}

{% step %}
**Trigger a sync on demand** Click **Trigger now** next to the job you want to run. The new run appears at the top of the **Recent Runs** table within moments.
{% endstep %}

{% step %}
**Investigate a failed run** Find the run in the **Recent Runs** table and check the **Error** and **Retries** columns. Click the action for that run to view full details.
{% endstep %}

{% step %}
**Create a new scheduled job** Click **Create a New Job** in the top-right corner, fill in the job name, schedule cadence, event type, and target, then save.
{% endstep %}
{% endstepper %}

## Related

* [Connector Schedule](/feature-reference/connectors/schedule.md)
* [Scheduling & Orchestration](/feature-reference/scheduling-orchestration.md)
* [Sync Types](/core-concepts/sync-types.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 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://docs.aohwv.dev/feature-reference/schedule.md?ask=<question>&goal=<endgoal>
```

`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.