> ## Documentation Index
> Fetch the complete documentation index at: https://docs.axottle.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Schedules

> Regular launch of playbooks: days of the week, time zone, skips, fixed goals and history.

The schedule creates Telepúrte tasks at selected local times daily or by day of the week. It stores a specific version of the playbook and an accurate list of nodes. Changing the group or adding new servers does not automatically extend the existing schedule.

## Make it from a playbook.

1. In **Playbooks and Schedules**, select the verified script and press **Launch**.
2. Select nodes, groups or tags and get a preview.
3. Version, steps, and a complete list of goals.
4. In the last step, select **on schedule**.
5. Specify the time zone, hour, minute and days of the week.
6. Choose what to do with the lost time and save it.

Use an IANA time zone name, such as `Asia/Yekaterinburg`, or `UTC`. Time refers to the selected zone, not necessarily to the time zone of the server or browser.

Although the interface may call launches cron schedules, the form specifies the time and days of the week, and the five-field arbitrary expression is not entered into it.

## An example of regular diagnosis

Create a playbook with **Diagnostics host**, check it manually on selected nodes. Then set 09:00, `Asia/Yekaterinburg`, Monday-Friday and **Skip** at skip.

In the list, check **Next launch of**, number of targets and status. After the time comes, open the schedule history, then the task created and the results of the nodes. The diagnostic snapshot shows the state at the time of execution, not continuous monitoring.

## Scheduling changes

Routinely running a script can change servers in the same way as manual. Confirmation refers to a specific scenario and goals; check for repeatability and recovery before creating.

For typed modifying actions, such as restarting a service or applying a file, the server requires explicit permission to change and rollout with a canary. Advanced rollout configuration is done via the preview API; the current wizard does not have these fields. If such a scenario is rejected, this restriction cannot be circumvented by pressing a button again. Use the correct API preview or manual launch.

Script-only scripts support independent targets without the need for a canary, so a normal scripting schedule should not be considered a protected automatic stoppage of the entire park after a first error. [task](https://docs.axottle.com/en/telepurte/jobs.md).

## Passes and intersections

| Policy/event | Behavior | |
| - | - | - |
| **Let it pass.** | When more than five minutes are late, the moment is missed. | |
| **Perform one time** | After downtime, one catch-up task is created, rather than a separate | for each missed day. |
| Previous job still running | New moment gets `skipped_overlap` | |
| Target or Agent Unavailable in | Test Offensive Ends with Error Without Partial | |
| Playbook version changed | `recipe_changed`, schedule switched off | |

On the day of the clock transfer, the missing local time is skipped, the repeating hour does not create two normal starts in one calendar day.

## Service window through API

The schedule API further supports `maintenance_window` and the `ends_at` deadline. The window is set by local time and must contain the assigned moment; the end before the start means the transition through midnight.

A catch-up run is only possible while the corresponding window is open. Upon closing, the event receives a `skipped_window`. The window restricts the output of further work, but is not a general automatic rollback of actions already performed.

These settings should not be searched for in the current basic form: they refer to the advanced configuration of the `/api/v1/schedules` API.

## Pause, renewal and modification

Open the schedule from the list, see the rule, the goals, and the history of the offensives. The suspension prohibits future launches, but does not stop the task already created - stop it separately.

Resume calculates the next future moment without reproducing all pause period omissions. If the playbook is modified or archived, create a new preview and schedule for the current version.

## Verification

Check the time zone, days, next run, number of nodes and skip policy. After the first advance, open the created task and the final results. "Active" state means the rule turned on, not the success of the last execution.

## Rollback

Suspend the schedule, stop an unnecessary active task, and restore the changes separately. To replace the rule, first prepare and check a new one, then eliminate the simultaneous operation of two schedules on the same servers.

Extended parameters, designated as APIs, may not be present in the current interface form.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.