AWS Security ChangesHomeSearch

AWS quick low security documentation change

Service: quick · 2026-03-22 · Security-related low

File: quick/latest/userguide/schedules-in-quick-flows.md

Summary

Revised notification section to include flow unsharing/deletion alerts

Security assessment

Added notifications for when flows with schedules are unshared or deleted, which helps users detect unauthorized access changes to sensitive automated workflows.

Diff

diff --git a/quick/latest/userguide/schedules-in-quick-flows.md b/quick/latest/userguide/schedules-in-quick-flows.md
index 7d2457119..e80a8a47c 100644
--- a//quick/latest/userguide/schedules-in-quick-flows.md
+++ b//quick/latest/userguide/schedules-in-quick-flows.md
@@ -5 +5 @@
-Creating schedulesManaging schedulesNotifications for schedule runsAuthentication and action handling in flow schedules
+Creating a scheduleManaging schedulesSchedule historyNotificationsAuthentication for action connectors
@@ -9 +9 @@ Creating schedulesManaging schedulesNotifications for schedule runsAuthenticatio
-Schedules in Amazon Quick Flows enables users to automate recurring, unattended flow executions. This feature allows business users to set up workflows that run automatically at specified times without manual intervention. This capability is great for automating routine and administrative tasks such as generating recurring reports from dashboards, summarizing open items assigned to you in external services, or generating daily meeting briefings before you head out to work. Users can configure schedules to flow that are created by them or to flows that are shared with them.
+Schedules let you automate recurring flow runs without manual intervention. You can schedule flows you have created or flows that have been shared with you. All schedules are private to you and cannot be shared with other users.
@@ -11 +11 @@ Schedules in Amazon Quick Flows enables users to automate recurring, unattended
-To create a schedule, open your flow and choose the scheduling icon. You configure the schedule by providing a name and description, defining the frequency, adding default inputs for the schedule run, and setting action permissions for any action steps. After you create a schedule, you can edit, pause, duplicate, or view runs directly from the schedule interface. All schedules you configure are private to you and cannot be shared with other users.
+Common uses include generating recurring reports, summarizing open items from external services, or preparing daily meeting briefings.
@@ -13 +13 @@ To create a schedule, open your flow and choose the scheduling icon. You configu
-You can view schedules for a specific flow from the flow run page, or view all your schedules across all flows from the My schedules tab in the flows library. When a scheduled flow completes successfully, you receive an email notification with a link to the completed run. You also receive notifications when a schedule run requires your input to continue, when a run fails, or when a flow with your schedules is unshared from you. The flow run history displays all runs—both scheduled and manual—for your review.
+## Creating a schedule
@@ -15 +15 @@ You can view schedules for a specific flow from the flow run page, or view all y
-## Creating schedules
+  1. Open your flow in Run mode.
@@ -17,23 +17 @@ You can view schedules for a specific flow from the flow run page, or view all y
-Users can create schedules directly in the flows runtime.
-
-###### To create a schedule
-
-  1. Sign in to the Amazon Quick console.
-
-  2. In the navigation pane, choose **Flows**.
-
-  3. Choose the flow name to open it in runtime mode.
-
-  4. Choose the scheduling icon.
-
-  5. Choose **Create schedule**.
-
-  6. Configure your schedule settings:
-
-     * **Schedule name** \- Enter a unique name for your schedule.
-
-     * **Description** \- (Optional) Provide details about the schedule's purpose.
-
-     * **Repeat configuration** \- Choose from system-generated suggestions or configure custom recurrence.
-
-  7. For custom recurrence, specify the following:
+  2. Choose the scheduling icon.
@@ -41 +19 @@ Users can create schedules directly in the flows runtime.
-     * **Frequency** \- Choose **Daily** , **Weekly** , or **Monthly**.
+  3. Choose **Create schedule**.
@@ -43 +21 @@ Users can create schedules directly in the flows runtime.
-     * **Start date** \- Select when the schedule begins.
+  4. Configure your schedule:
@@ -45 +23 @@ Users can create schedules directly in the flows runtime.
-     * **End date** \- (Optional) Select when the schedule ends.
+     * **Schedule name** — A unique name for the schedule.
@@ -47 +25 @@ Users can create schedules directly in the flows runtime.
-     * **Time zone** \- Choose the time zone for schedule execution.
+     * **Description** — Optional. Details about the schedule's purpose.
@@ -49 +27 @@ Users can create schedules directly in the flows runtime.
-  8. Choose **Next**.
+     * **Repeat configuration** — Choose from suggestions or configure custom recurrence (daily, weekly, or monthly) with start date, optional end date, and time zone.
@@ -51 +29 @@ Users can create schedules directly in the flows runtime.
-  9. Provide default inputs that the schedule uses during each run.
+  5. Choose **Next**.
@@ -53 +31 @@ Users can create schedules directly in the flows runtime.
-###### Note
+  6. Provide default inputs for each scheduled run.
@@ -55 +33 @@ Users can create schedules directly in the flows runtime.
-Depending on the flow, you will be required to add multiple files or provide multiple text inputs.
+  7. Choose **Next**.
@@ -57,3 +35 @@ Depending on the flow, you will be required to add multiple files or provide mul
-  10. Choose **Next**.
-
-  11. Configure action permissions:
+  8. Configure action permissions:
@@ -63,9 +39 @@ Depending on the flow, you will be required to add multiple files or provide mul
-     * Turn off this option if you want to review and confirm each action manually.
-
-###### Note
-
-Action permissions only appear if there are read action steps set up in the flow.
-
-  12. Choose **Save**.
-
-
+     * Turn off to review and confirm each action manually.
@@ -72,0 +41 @@ Action permissions only appear if there are read action steps set up in the flow
+  9. Choose **Save**.
@@ -74 +42,0 @@ Action permissions only appear if there are read action steps set up in the flow
-### Schedule frequency options
@@ -76,5 +43,0 @@ Action permissions only appear if there are read action steps set up in the flow
-  * **Daily** : Run every X day(s) with start date, end date and time zone configurable.
-
-  * **Weekly** : Run every week on selected day(s) of the week with start date, end date and time zone configurable.
-
-  * **Monthly** : Run on a specific day of the month with start date, end date and time zone configurable.
@@ -82,0 +46 @@ Action permissions only appear if there are read action steps set up in the flow
+###### Note
@@ -83,0 +48 @@ Action permissions only appear if there are read action steps set up in the flow
+Action permissions only appear if the flow contains action steps. Automatic form submission is enabled by default for write actions. User confirmation is recommended to help avoid AI prediction errors.
@@ -87,28 +52 @@ Action permissions only appear if there are read action steps set up in the flow
-### Managing schedules from the flow runtime page
-
-From the flow runtime page, you can access schedules associated with that specific flow.
-
-###### To manage schedules for a flow
-
-  1. Open your flow in runtime mode.
-
-  2. Choose the scheduling icon.
-
-  3. Choose one of the following actions:
-
-     * **Create schedule** \- Create a new schedule for the flow.
-
-     * **Edit** \- Modify an existing schedule's configuration.
-
-     * **Pause** \- Temporarily stop a schedule from running.
-
-     * **Duplicate** \- Create a copy of an existing schedule.
-
-     * **View runs** \- Opens the run history for the schedule.
-
-     * **Delete** \- Permanently remove the schedule.
-
-
-
-
-### Managing schedules from the flows library
+You can manage schedules from two places:
@@ -116 +54 @@ From the flow runtime page, you can access schedules associated with that specif
-The **Schedules** tab in the flows library provides a centralized view of all your schedules across all flows.
+  * **From the flow** — Open the flow, choose the scheduling icon, and edit, pause, duplicate, view runs, or delete a schedule.
@@ -118 +56 @@ The **Schedules** tab in the flows library provides a centralized view of all yo
-###### To access all your schedules
+  * **From the Flows library** — Choose the **My schedules** tab to see all your schedules across all flows with their status, frequency, last run, and associated flow name.
@@ -120 +57,0 @@ The **Schedules** tab in the flows library provides a centralized view of all yo
-  1. In the navigation pane, choose **Flows**.
@@ -122 +58,0 @@ The **Schedules** tab in the flows library provides a centralized view of all yo
-  2. Choose the **Schedules** tab.
@@ -124,0 +61 @@ The **Schedules** tab in the flows library provides a centralized view of all yo
+## Schedule history
@@ -125,0 +63 @@ The **Schedules** tab in the flows library provides a centralized view of all yo
+All manual and scheduled runs appear in the flow run history. You can filter by all runs, scheduled runs, or failed runs. History is retained for 30 days.
@@ -127 +65 @@ The **Schedules** tab in the flows library provides a centralized view of all yo
-The Schedules tab displays the following information:
+Visual indicators help distinguish run types:
@@ -129 +67 @@ The Schedules tab displays the following information:
-  * **Status** \- Whether the schedule is active or paused.
+  * Schedule run tag for scheduled runs
@@ -131 +69 @@ The Schedules tab displays the following information:
-  * **Schedule name** \- The name you assigned to the schedule.
+  * Orange dot for un-viewed completed runs
@@ -133 +71 @@ The Schedules tab displays the following information:
-  * **Repeat configuration** \- The frequency and timing settings.
+  * Running tag for in-progress runs
@@ -135,22 +73 @@ The Schedules tab displays the following information:
-  * **Last run status** \- The time of the most recent execution.
-
-  * **Flow name** \- The flow associated with the schedule.
-
-
-
-
-From this view, you can edit, pause, duplicate, view run history, or delete any schedule.
-
-### Schedule history and auditing
-
-All manual and scheduled runs are available for users in the flow run history. For completed scheduled run, the history highlights the name of the schedule, status of the schedule (completed, running, unread) and schedule run time. Users get filters to view all runs, scheduled runs, and failed runs. Users can open any completed run through history and follow up.
-
-**Visual indicators:**
-
-  * Schedule run tag differentiates scheduled runs from manual runs.
-
-  * Orange dot indicator for un-viewed completed scheduled runs.
-
-  * Running tag for schedules that are currently running.
-
-  * Failed tag for scheduled runs that failed.
+  * Failed tag for failed runs
@@ -163,12 +80 @@ All manual and scheduled runs are available for users in the flow run history. F
-Users cannot view ongoing scheduled runs till the run is complete.
-
-**Filtering and search:**
-
-  * Filter by completed scheduled runs, all runs, failed runs.
-
-  * Search through your history. History persists for 30 days.
-
-
-
-
-## Notifications for schedule runs
+You cannot view an ongoing scheduled run until it completes.
@@ -176 +82 @@ Users cannot view ongoing scheduled runs till the run is complete.
-Users receive email notifications for:
+## Notifications
@@ -178 +84 @@ Users receive email notifications for:
-  1. **Successful completion:** On successful schedule run complete, users get an email notification. The email notification contains a link that takes users view the completed flow run.
+You receive email notifications when:
@@ -180 +86 @@ Users receive email notifications for:
-  2. **Schedule run requires human input:** If the flow run requires human input to continue, users receive an email notification asking for input. The email notification contains flow link that takes user to the paused flow run where they can enter their inputs.