> For the complete documentation index, see [llms.txt](https://docs.erathos.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.erathos.com/platform/connections/sync-schedule.md). # Sync schedule The primary function of a data pipeline is to keep two environments synchronized. To achieve this, pipelines rely on scheduled data update executions. These schedules are typically based on a specific **time** and an **update frequency**. ## Base hour The **Base Hour** refers to the specific time of day at which a scheduled pipeline execution begins, serving as the anchor point for the selected update frequency (e.g., weekly, daily, or every 12 hours). All subsequent executions follow this base hour based on the defined frequency. ## Frequency The available update frequencies on the Alexandria platform are: * **Manually:** Executes only when trigged by user. * **Weekly**: Executes once every week. * **Daily**: Executes every 24 hours. * **Every 12 Hours**: Executes every 12 hours. * **Every 6 Hours**: Executes every 6 hours. * **Every 3 Hours**: Executes every 3 hours. * **Every Hour**: Executes every 1 hour. * **Every 30 Minutes**: Executes every 30 minutes. * **Every 5 Minutes**: Executes every 5 minutes. ## Using sync frequencies and base hour {% embed url="" %} --- # 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.erathos.com/platform/connections/sync-schedule.md?ask=&goal= ``` `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.