> 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/patch-my-pc-publisher/manage/sync-schedule-tab/overview.md).
# Overview of the Scheduling tab in Patch My PC Publisher
*Applies to: Patch My PC Publisher V3.x*
The **Sync Schedule** tab in Patch My PC (PMPC) Publisher controls when Publisher runs an automated *publishing sync*.
A *publishing sync* evaluates third party apps and updates, and publishes content based on the configured selections in the Product Trees, customizations, and global options across the tabs.
## How a Publishing Sync Works
A *publishing sync* represents the evaluation of publishing intent at a specific point in time. During the first sync, Publisher evaluates all configured selections across the **WSUS Updates**, **ConfigMgr Apps**, **Intune Apps**, and **Intune Updates** tabs, along with any customizations and global options configured throughout the console. These settings define what content Publisher is expected to publish.
At the start of every publishing sync, Publisher downloads and processes the latest version of the Patch My PC catalog. Each sync always evaluates the most current catalog data available.
After the catalog is loaded, Publisher evaluates the selected products across all publishing tabs. For each selected app or update, Publisher checks whether the version in the catalog has already been published. If the version has not been published, Publisher publishes the new version using the configured options and customizations.
## Sync Schedule Recommendations
The primary purpose of the Sync Schedule is to continuously evaluate the latest third party apps and updates as they are released by vendors. Third-party vendors do not release updates on a single predictable schedule, and new versions can be released at any time, particularly for products such as browsers and collaboration tools.
As each sync evaluates the latest version available in the catalog, the configured schedule directly determines how quickly newly released content is detected and made available for deployment.
The default configuration is a daily sync, which is suitable for most environments. Running the sync infrequently, such as on a monthly schedule, is generally not recommended unless strict operational processes require that frequency.
Infrequent synchronization can result in missed security updates and delayed visibility of newly released third party content. The Sync Schedule should be configured to run as often as practical based on operational constraints.
## How Deployment Timing Is Controlled
The Sync Schedule determines when apps and updates are published, not inherently when they are installed on devices. How quickly they are deployed to clients is dictated by the target management platform and the configuration applied either within the Publisher or natively in the platform:
* [Intune Apps & Updates](#intune-apps-and-updates)
* [WSUS/ConfigMgr Updates](#wsus-configmgr-updates)
* [ConfigMgr Apps](#configmgr-apps)
### Intune Apps & Updates
For Intune apps and Intune updates, assignments can be configured directly in Publisher. These assignments define targeting, availability, deadline, and other deployment behaviors, which ultimately control when apps and updates are delivered to devices after they have been published.
### WSUS/ConfigMgr Updates
For updates published in a standalone WSUS environment, deployment timing is controlled through update approvals. Administrators can manually approve updates or use WSUS auto approval rules to manage when updates become available to devices.
For updates synced to ConfigMgr from WSUS after they are published, deployment cadence can be controlled using Automatic Deployment Rules (ADRs). ADRs define availability and deadline behavior and allow staged or delayed rollouts.
### ConfigMgr Apps
For ConfigMgr apps, Publisher is responsible only for creating the applications. Deployment targeting and timing are fully controlled by administrators using standard ConfigMgr deployment practices.
{% hint style="info" %}
**Note**
If the [global option to update an application in place](/patch-my-pc-publisher/manage/configmgr-apps-tab/base-install-options/application-creation-options.md#update-existing-applications-metadata-deployment-type-detection-method-and-content-files-default) is enabled, newly published app versions will inherit existing deployments. For required deployments, this inheritance may directly influence how quickly devices receive the updated application.
{% endhint %}
---
# 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.patchmypc.com/patch-my-pc-publisher/manage/sync-schedule-tab/overview.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.