Current Limitation: Quick Flows currently require manual approval for each execution, even after a flow has been thoroughly tested and proven reliable over multiple successful runs.
Business Impact:
Reduces the automation benefit of flows, as they still require human intervention
Creates bottlenecks when flows need to run during off-hours or when approvers are unavailable
Limits the scalability of workflow automation across teams
Prevents truly “hands-off” automation for repetitive, well-established processes
Proposed Enhancement: After a flow has demonstrated reliability (e.g., 10+ successful executions, or after a defined confidence period), provide an option to:
Enable “auto-approve” mode for that specific flow
Set conditions under which auto-approval applies (e.g., same input parameters, scheduled runs only)
Maintain audit logs of all executions for compliance
Allow administrators to revert to manual approval if needed
Use Case Example: A daily report generation flow that has run successfully for 30 days should be able to continue running independently without requiring manual approval each time, while still maintaining full audit trails and the ability to pause/review if anomalies are detected.
Expected Benefit: This would allow teams to take full advantage of Quick Flows’ automation capabilities while maintaining appropriate governance and oversight for new or modified workflows.
Hi @Fernando_Schmitt – Welcome to the community. Have you explored this new feature of scheduling the Quick flows? 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.
Yeah, I have already a scheduled flow. However, when the flow reaches the step to send a slack message, it waits for manual validation / confirmation / someone to click the send button. So, this is what I’m trying to improve with this story. I would understand the first runs to require that but, after a couple, that should not be the case anymore.
Hope everything is well! Just wanted to check in to see if you are still encountering this behavior. I am wondering if the reason the ‘no confirmation’ option does not pop up for Rishi_Palanikumar because you are not able to an existing but can do so for creating a new schedule. I would definitely try creating a new one to see if that is the case and make sure that option appears for you.
However, I also found a previous thread listed here that indicates that despite the option being available, it still may not work as intended. I will make sure to keep this post marked as a Feature Request to promote further awareness to the AWS Team, but please feel free to let me know how creating a new schedule works for you in the meantime!
If that workaround does not work (and since this does seem to be an account-based issue), I would definitely recommend reaching out to a respective IT admin or other respective Amazon internal channels to see if a permissions change fixes the issue.
