> For the complete documentation index, see [llms.txt](https://docs.patchmypc.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.patchmypc.com/installation-guides/configmgr/sync-schedule.md).

# Sync Schedule

Getting started with a Sync Schedule for the patch my pc publisher and understanding product timing.

*Applies to: On-premises Publisher*

## Scheduling Daily Publish

By default, we recommend the Publisher sync runs on a daily basis. The sync schedule only controls **when updates or applications are published** to your environment. Patch My PC does **not automatically create deployments** in Configuration Manager for you.

{% hint style="success" %}
**Tip**: Generally, Patch My PC releases an update to the catalog **three to five times a week**. These updates are released usually posted by **4:00 PM Eastern Time**.
{% endhint %}

When Patch My PC releases these new updates, the **sync schedule is what automates the publication process**. You can also manually start the sync and publication process at any time by selecting the **Run Publishing Service Sync** option.

![Publishing Schedule](https://3773699522-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MX7dvS0r_4fc0AikgJS%2F-MY5hkZ2tQ7eajUtYWRd%2F-MY5lOXtxf44jC9OlyeZ%2Fimage.png?alt=media\&token=3eebd74f-77fc-4b10-b40a-cd0828b0fe16)


---

# 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://docs.patchmypc.com/installation-guides/configmgr/sync-schedule.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.