> For the complete documentation index, see [llms.txt](https://docs.adaptiva.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.adaptiva.com/platform-guide/platform-features/schedules.md). # Schedules Describes how to use and configure schedules in OneSite Platform Schedules automate the delivery of content, the execution of Workflows, updating Groups, and the delivery of some notifications. There are several default Schedules you can choose from or modify, or you can create your own custom schedule. ![](https://4278434842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6zWDkRrsxRGskacChCcP%2Fuploads%2Fgit-blob-ed3483ac79bdc90b69cfbb4ebae1c3ef976516c2%2Fdefault-schedules.png?alt=media) {% hint style="info" %} We recommend that you open one of our default Schedules, select **More > Save As**, then modify the copy rather than creating a brand new Schedule. {% endhint %} ## View schedule settings When creating or modifying a schedule, you will have multiple settings to configure. Below is a description of each setting and some possible use cases. ### General settings ![](https://4278434842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6zWDkRrsxRGskacChCcP%2Fuploads%2Fgit-blob-5abec641a1bd017b942a52631e82ba7341dea504%2Fgeneral-settings.png?alt=media) #### Name * You'll want a unique name for your schedule that describes when it runs. You will use this later for actions like Patch Strategy executions. * e.g. - Wed after Patch Tuesday - 4pm #### Description * You can optionally add a description that will add more context especially for similar schedules. * E.g. - This schedule is set to run the second Wednesday of every month at 4pm. ### Schedule Settings ![](https://4278434842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6zWDkRrsxRGskacChCcP%2Fuploads%2Fgit-blob-5774534a7e92420f873607c911452a14885e32cf%2Fschedule-settings-default.png?alt=media) #### Use Server TimeZone * This setting is disabled by default and will use the local time zone. If you enable this setting, the schedule will be based off the timezone set in the server settings.

Make sure that you are aware of what time zone the server is using.

For SaaS installations, if the server time zone has not explicitly been set then its value will be Default Time Zone, which is UTC+0.

On premises installations use the local time zone of the device it is installed on.

You can check the server time zone setting by clicking on the gear icon in the upper right and selecting settings > about.

* Use case of Local Timezone * You set the schedule to run at 6 AM local machine time for your Seattle Location (PST) clients to receive content. New York clients have a separate schedule to also run at 6 AM EST local machine time. This ensures that the New York Location's working hours are unaffected by a PST schedule. * Use case of Server Timezone * You toggle on **Use Server Timezone** (CST) and set the schedule to 4 AM. New York and Seattle clients receive their content at 5 AM and 3 AM respectively. This ensures both Locations receive content at the same time in their different timezones. #### Start/End Time * You must specify at least a **Start time** and an optional **End time** that requires **Enable End Time** to be enabled. * Use case of end time * You set your Schedule to run every hour between 11/01 7 AM and 11/01 11:59 PM to receive Dashboard Subscription notifications to monitor Deployment Status for new Tucson location clients. #### Execution Offset * The amount of time before or after the Schedule's start time to execute a recurring action. Only applies to recurring schedule types. #### Schedule Repeat * By default this is set to ASAP. You can select recurring times or **Not Recurring** so it only runs a single time once deployed and added to an object. ### Additional Time Constraints When enabled, you can more granularly configure time slots to ensure the object is scheduled around any time constraints like working hours or business events. ![](https://4278434842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6zWDkRrsxRGskacChCcP%2Fuploads%2Fgit-blob-8cebdb11948b322ae21da1ced7526808a0089627%2Fadditional-time-constraints.png?alt=media) #### Time slots * You can add time slots to define when you don't want your Schedule to run. * Use case * Your business has regular server maintenance on Tuesdays. You want to create a schedule that runs every hour of each day, except during working hours on Tuesdays. You can create a Schedule with Recurring Interval set to 1 hour, and add a time slot for Tuesdays between 7 AM and 7 PM. ![](https://4278434842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6zWDkRrsxRGskacChCcP%2Fuploads%2Fgit-blob-17181dfc5ef69827dbf32741986da1d5157a75df%2Fnew-time-slot.png?alt=media) #### Load Leveling Duration * Adaptiva balances the load so clients are targeted in smaller subsets within a set **Load Leveling Duration** duration instead of all clients targeted at the same time. * Use case * You have 100 clients set to receive some content via a custom Schedule. The custom Schedule is configured to run every Sunday at 2 a.m and has a load leveling Duration of two hours. This will assign to each device a random time within the load level window to receive content. If the devices are not available during this window they will wait until the next Sunday at 2 a.m. #### Set Override Duration {% hint style="info" %} We recommend you work with our [Adaptiva Support Team](https://adaptiva.com/support) before you enable Override Duration. {% endhint %} * Override Duration sets a timer at the end of the specified time slots. When the Override Duration has expired, Schedules will run ASAP. * Use case * You have 100 clients who are scheduled to receive a patch every Sunday between the hours of 2 AM and 4 AM. Of the 100 clients, only 96 clients receive the patch during that load leveling duration. The last four clients were not powered on and therefore will have to wait until the following Sunday when the schedule runs again. However, you have set your Override Duration to 8 hours. So, once the 8 hours has passed, the schedule will run again at 10 a.m. (8 hours from the start time) on Monday for those remaining clients. ## Create a custom Schedule In the example below, we'll be creating a new Schedule that you can use in your Patch Tuesday strategy. 1. Click **Schedules** from the side bar navigation in the Admin Portal. ![](https://4278434842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6zWDkRrsxRGskacChCcP%2Fuploads%2Fgit-blob-952aafb783fc95ee69e849e2694e0bf43428c804%2Fschedules-admin-portal-side-bar-nav.png?alt=media) 2. Click **New**. 3. In the Schedule editor, configure the following settings: **General Settings** ![](https://4278434842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6zWDkRrsxRGskacChCcP%2Fuploads%2Fgit-blob-5abec641a1bd017b942a52631e82ba7341dea504%2Fgeneral-settings.png?alt=media) * **Name** - Enter a name of *Wednesday after Patch Tuesday - 4pm*. * **Description** - Enter a description of *This schedule is set to run the second Wednesday of every month at 4pm*. **Schedule Settings** ![](https://4278434842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6zWDkRrsxRGskacChCcP%2Fuploads%2Fgit-blob-45983fb9c07677573d7c48db036147ecdbf804ea%2Fschedule-settings-demo.png?alt=media) * **Start/End Time** - Enter a **Start Time** for today at 4pm. * **Execution Offset** - Enter **1 Day** for the offset. * **Schedule Repeat** - Select **Recurring Monthly by Day Of The Week**. * **Month by Week Setting** - Select **Tuesday** from **Day of the Week** and enter **2** for **Week of the Month**. 4. Click **Save and Deploy**. This schedule will execute one day after the second Tuesday of each Month (Patch Tuesday) at 4pm. You can now use this schedule for your Patch Tuesday patching strategy to ensure Windows patches are available for all devices in your organization.