> 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/connectors/schedule.md).

# Schedule

The Schedule tab shows the automated Sync schedules configured for this Connector, which control when AOH Sync runs a Sync automatically.

![The Schedule tab for AOH Test AD → CloudSync (Delta), showing the Sync Schedules section with a note that no scheduled jobs exist yet and that they are created automatically when a Target System is added](/files/bSL0v1QOvEiIxCU6S4JM)

*The Schedule tab displays any automated Sync schedules assigned to this Connector.*

## What you can do here

| Action              | What it does                                                                             |
| ------------------- | ---------------------------------------------------------------------------------------- |
| View scheduled jobs | See the list of recurring Sync schedules that will trigger this Connector automatically. |

## How schedules work

AOH Sync Sync Schedules are created automatically when you add a Target System — you do not need to define them manually. The platform seeds the standard delta and full sync cadences for you based on your Target System configuration.

If no Target System has been connected to this Connector yet, the Schedule tab shows a message indicating that no scheduled jobs exist. Once a Target System is added, the canonical schedule entries appear here.

{% hint style="info" %}
To trigger a Sync immediately without waiting for the next scheduled run, use the **Run Now** button on the Connectors list page.
{% endhint %}

## Related

* [Sync Types](/core-concepts/sync-types.md)
* [Connector Overview](/feature-reference/connectors/overview.md)
* [Sync History](/feature-reference/connectors/logs.md)
* [Connectors](/feature-reference/connectors.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/connectors/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.