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.
   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.

Figure 1 — Schedules tab