I apologize on the late reply. Is your question still unresolved or have you found a solution in the meantime?
What you potentially can do is build in a form of if/else logic in your flows. Essentially build in specific rule conditions within your prompts. For example, it can potentially structured so that the flow checks the folder status first, then uses an if/else logic where the “if emails exist” path runs your current sequence, and the “else” path (empty folder) can proceed to a different step or ignore certain steps. Hopefully this way can help reduce or stop the notification you are getting. It may not be the perfect solution but I would recommend trying it out.
So when creating a schedule, there is an option to ‘run with no confirmation’ as seen as the screenshot below, but this on I still believe it requires approval.
From how I currently understand it, Flows will always ask you to approve certain actions like sending slack messages or outlook emails. The reasoning that AWS has given us is that it helps keep the human in the loop. Other users have expressed the same issue about always having to approve certain actions and I believe on a user series call they mentioned that reducing the number of approvals is on the roadmap. With that, I would recommend keeping an eye out on the ‘What’s New’ page for any relevant updates (Latest What’s New topics - Amazon Quick Suite Community).
Just checking back in since we haven’t heard from you in a bit. I wanted to see if the guidance shared earlier helped resolve your question, or if you found a solution in the meantime.
If you still have any additional questions related to your initial post, feel free to share them. Otherwise, any update you’re able to provide within the next 3 business days would be helpful for the community.
My two thoughts that might be the cause of that is either the status of your slack integration is not ‘available’ or the specific slack action that you are trying to do does not support the ‘run with no confirmation’ option. Nonetheless, even with the ‘run with no confirmation’ turned on I believe it will still require that layer of approval to send any message through slack.
What I can do is attach the ‘feature-request’ tag to this post in regard to the automating the action of sending slack messages which can help increase visibility to the Quick Team.