You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: synthetics/test-config/syn-downtimes.rst
+20-6Lines changed: 20 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -28,8 +28,8 @@ The best practice is to schedule a downtime configuration with a 15 to 30 minute
28
28
29
29
Schedule requirements:
30
30
31
-
* Downtimes configurations must be at least fifteen minutes long.
32
-
* Downtimes configurations can be a maximum of one year in advance and one year in duration.
31
+
* Downtime configurations must be at least fifteen minutes long.
32
+
* Downtime configurations can be a maximum of one year in advance and one year in duration.
33
33
34
34
How to schedule a downtime configuration:
35
35
@@ -41,15 +41,29 @@ How to schedule a downtime configuration:
41
41
#. Select :guilabel:`Create`.
42
42
43
43
44
-
When a recurring downtime configuration is active, you can't edit, delete, or extend it, but you can end it immediately. When a non-recurring downtime configuration is active, you can't edit or delete it, but you can extend its duration or end it immediately.
If you selected a value other than :guilabel:`Does not repeat` in the :guilabel:`Recurrence` menu, the :guilabel:`Create a downtime configuration` form displays a preview of the first ten downtime configurations.
* If it's non-recurring you can edit or delete it.
56
+
* If it's recurring you can edit it, but you can only delete it before its first run. Its status may still be displayed as :guilabel:`Scheduled`, but it's functionally locked after the first occurrence.
57
+
* To delete a downtime configuration, select the :guilabel:`Delete` action from the vertical dot menu (|verticaldots|).
58
+
59
+
* While a downtime configuration is active:
60
+
61
+
* If it's non-recurring you can't edit or delete it, but you can extend it or end it immediately.
62
+
* If it's recurring you can't edit, delete, or extend it, but you can end it immediately.
63
+
64
+
* After the first run of a downtime configuration, whether it's recurring or not, you can't delete or edit it.
0 commit comments