> For the complete documentation index, see [llms.txt](https://docs.tessell.com/tessell/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.tessell.com/tessell/database-engines/tessell-for-postgresql/db-services/readme-postgresql/homepage-postgresql/schedules-postgresql.md).

# Schedules

The Schedules tab lets you automate service lifecycle actions. You can configure start/stop schedules to reduce costs outside business hours, delete schedules to decommission services at a set time, and view or manage refresh schedules for cloned services.

***

## How do I create a start/stop schedule?

Three recurrence patterns are supported:

| Repeat option       | Behaviour                                                                                                       |
| ------------------- | --------------------------------------------------------------------------------------------------------------- |
| **Does not repeat** | Runs once at the configured date and time.                                                                      |
| **Daily**           | Runs every day at the configured start time. End repetition: Never, On a specific date, or After N occurrences. |
| **Weekly**          | Runs on selected days of the week. End repetition: Never or On a specific date.                                 |

### Steps to create a start/stop schedule

1. Click **Add** on the right side of the Start/Stop Schedule section.
2. In the **Create Schedule** window:
   * Select a **Repeat** option (Does not repeat, Daily, or Weekly).
   * For **Weekly**, select the days of the week to run.
   * Configure the end-repetition preference: Never, On a date, or After N occurrences.
   * Set the **start day and time** under Duration.
3. Click **Submit**.

The configured schedule appears below the Start/Stop Schedule header showing:

| Column         | Description                                         |
| -------------- | --------------------------------------------------- |
| **Start date** | The date the schedule begins.                       |
| **Duration**   | How long the database service runs before stopping. |
| **Repeat**     | Recurrence: Does not repeat, Daily, or Weekly.      |

As an alternative, use the **Code** button to view, copy, or download the schedule code in Shell, Python, Go, Java, JavaScript, or PowerShell.

***

## How do I configure a delete schedule?

You can control whether a final snapshot is taken and whether the Availability Machine is retained.

### Steps to create a delete schedule

1. Click **Add** on the right side of the Delete Schedule section.
2. Pick the **Deletion date** (calendar icon) and **Deletion time** (clock icon).
3. (Optional) Select **Take a final snapshot before deletion** to create a standalone manual snapshot at the scheduled deletion time. This snapshot is independent of the Availability Machine.
   * Specify a name in **Snapshot Name**, or use the auto-generated name.
4. Choose how to handle the Availability Machine using the **Retain existing data in the Availability Machine** checkbox:

   | Option                                                                   | What is retained                                                                                                                                                                                                                                                  |
   | ------------------------------------------------------------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
   | **Checked** → All existing data (snapshots, backups, WAL logs, and DAPs) | Availability Machine and all its contents are retained and continue to age out per the existing RPO policy.                                                                                                                                                       |
   | **Checked** → Starred snapshots & backups only                           | Only starred snapshots/backups are retained; all other snapshots, backups, WAL logs, and DAPs are deleted. See [Star a snapshot or backup](/tessell/database-engines/tessell-for-postgresql/db-services/am-postgresql-doc.md#how-do-i-star-or-unstar-a-snapshot). |
   | **Unchecked**                                                            | Availability Machine and the database service are both deleted at the scheduled time.                                                                                                                                                                             |

   > If you selected **Take a final snapshot before deletion**, that snapshot is retained independently, even if you clear the Retain checkbox.
5. Click **Submit**.

The scheduled delete entry is displayed showing the deletion date/time, Availability Machine retention status, and whether a final snapshot is scheduled.

***

## How do I manage refresh schedules for cloned services?

For cloned services, existing refresh schedules are displayed in the Schedules tab. Click the ellipsis icon on a schedule entry to:

* **Update** — modify the schedule configuration.
* **Pause** — temporarily suspend the schedule without deleting it.
* **Delete** — remove the schedule permanently.

### When is a scheduled refresh skipped?

A scheduled refresh is marked as **SKIPPED** in two cases:

1. The database service is running another operation at the scheduled time (patching, instance addition, parameter profile update, snapshot in progress, etc.).
2. No recent snapshot is accessible to the schedule owner when the refresh is triggered.

<div align="center"><img src="https://3421475909-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FXNKiIctERJykfezXfUU2%2Fuploads%2Fgit-blob-ed4a14e17e5ac82f480a88ac33525ac0d2dbaf80%2Fschedules.png?alt=media" alt=""></div>

<p align="center"><em>Figure 1 — Schedules tab</em></p>


---

# 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.tessell.com/tessell/database-engines/tessell-for-postgresql/db-services/readme-postgresql/homepage-postgresql/schedules-postgresql.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.