From b1d7c27124ee98b671c311d7198edf81dc7c2eae Mon Sep 17 00:00:00 2001 From: Thomas Heartman Date: Fri, 12 Jan 2024 13:18:30 +0530 Subject: [PATCH] docs: add a note about suspended change request schedules (#5874) This PR describes in closer detail what happens when the user who scheduled a change request is deleted. It mentions the new suspended state and what the user can do to get out of it. --- website/docs/reference/change-requests.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/docs/reference/change-requests.md b/website/docs/reference/change-requests.md index 25a72b3896..a0bc68f8e0 100644 --- a/website/docs/reference/change-requests.md +++ b/website/docs/reference/change-requests.md @@ -91,7 +91,7 @@ When a scheduled change request is applied, the person who scheduled it and the #### Edge cases: what happens when ...? -If the user who scheduled a change request is deleted from the Unleash users list before the scheduled time, the changes will **not** be applied. +If the user who scheduled a change request is deleted from the Unleash users list before the scheduled time, the changes will **not** be applied. Instead, the schedule will be put into a special **suspended state**. A change request with suspended schedule will not be applied at its scheduled time. A user with the required permission can reschedule, apply, or reject the change request. Any of these actions will put the change request back into the regular flow. If a change request has been scheduled and change requests are then disabled for the project and environment, the change request **will still be applied** according to schedule. To prevent this, you can reject the scheduled change request.