Skip to content

Commit c52bc4a

Browse files
authored
Update articles/mysql/flexible-server/concepts-maintenance.md
1 parent 5b35c51 commit c52bc4a

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

articles/mysql/flexible-server/concepts-maintenance.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -44,7 +44,7 @@ You can define system-managed schedule or custom schedule for each flexible serv
4444
* With system-managed schedule, the system will pick any one-hour window between 11pm and 7am in your server's region time.
4545

4646
> [!IMPORTANT]
47-
> Previously, a 7-day deployment gap between system-managed and custom-managed schedules was maintained. Due to evolving maintenance demands and the introduction of the [maintenance reschedule feature (currently in public preview)](#maintenance-reschedule-public-preview), we can no longer guarantee this 7-day gap.
47+
> Previously, a 7-day deployment gap between system-managed and custom-managed schedules was maintained. Due to evolving maintenance demands and the introduction of the [maintenance reschedule feature (preview)](#maintenance-reschedule-preview), we can no longer guarantee this 7-day gap.
4848
4949
In rare cases, maintenance event can be canceled by the system or may fail to complete successfully. If the update fails, the update will be reverted, and the previous version of the binaries is restored. In such failed update scenarios, you may still experience restart of the server during the maintenance window. If the update is canceled or failed, the system will create a notification about canceled or failed maintenance event respectively notifying you. The next attempt to perform maintenance will be scheduled as per your current scheduling settings and you will receive notification about it five days in advance.
5050

0 commit comments

Comments
 (0)