> 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-tab/schedule/schedule.md). # Schedule section of Patch My PC Publisher *Applies to: Patch My PC Publisher V3.x* The **Schedule** section on the **Schedule** tab in Patch My PC (PMPC) Publisher allows you to configure when a Publisher sync occurs.
'Schedule' section
The available options are: * **Hourly**\ Use this option to run the publishing service at a recurring hourly interval. You specify the number of hours between each sync. The schedule begins as soon as the service starts and continues at the defined interval. * **Daily (Default)**\ Use this option to run the publishing service once per day. You configure the time using hour and minute selectors and choose **AM** or **PM**. The sync will start within five minutes of the configured time. * **Weekly**\ Use this option to run the publishing service once per week. You select the day of the week and the time. The sync runs on the chosen weekday at the specified time. * **Monthly**\ Use this option to run the publishing service once per month. You specify the day of the month and the time. * **Custom**\ Use this option to run the publishing service on a specific weekday pattern. You select the occurrence (first, second, third, or last), then select the weekday and time. An optional offset in days can be applied to shift the sync earlier or later than the calculated date. * **Disabled**\ Use this option to prevent the publishing service from running automatically. When selected, all publishing actions require a [manual sync](/patch-my-pc-publisher/manage/sync-tab/schedule/sync-status.md#run-publishing-service-sync). This is useful for testing or tightly controlled publishing environments. {% hint style="danger" %} **Important** Publisher uses a single, global Sync Schedule that applies across all tabs and products. You cannot configure different Sync Schedules per platform or product. {% endhint %} ## Next scheduled sync The **Next scheduled sync** field shows the date and time the next scheduled Sync Schedule will run, so you can check your understanding of how you think you've configured the Sync Schedule versus how Publisher will actually run it.
'Next scheduled sync'
## Run a missed scheduled sync on startup When you enable the **Run a missed scheduled sync on startup** option, Publisher will perform a sync as soon as possible. Enable this option if the Publisher service was offline at the time the Sync schedule was due to run.
Run a missed scheduled sync on startup
{% hint style="info" %} **Note** Manual syncs do not affect this option. {% endhint %} When you enable this option, the **Next scheduled sync** section updates to show the **Next sync if saved** entry, showing when the next Sync Schedule will run if you click **Apply** or **Save and Close**.
--- # 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/patch-my-pc-publisher/manage/sync-tab/schedule/schedule.md?ask=&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.