Recently a new future was added to Quick flow to allow auto execution for slack Personal DM in AmazonBI accounts. it was working fine in my flow until recently it started asking for permission to execute. Is there a sitting I need to change or what do I need to do for the flow to execute action to my slack without needing my approval. I tried re-running it multiple times incase it was an error but its asked me for permission every time. Any help on this would be greatly appreciated.
Hi @Mohamed_Anwer,
This is a known issue that others have reported. When you schedule a Flow, there’s an “Action permissions” step where you toggle on “Run with no confirmation”, which it sounds like you’ve already done. The fact that it was working and then stopped suggests either the setting got reset (sometimes editing a Flow can do this), or you’re hitting an intermittent platform bug.
First, I’d double-check that the “Run with no confirmation” toggle is still enabled in your schedule’s Action permissions step. This community thread covers the same issue with Slack connectors. If the toggle is still on and it’s still asking for permission, I’d recommend opening an AWS Support ticket, this appears to be a platform-side bug where the confirmation requirement fires regardless of the setting. Here is the link: Case management - AWS Support
Hope this helps and feel free to keep us posted!
hey @WLS-Cesar I dont have the option “run with no confirmation” when I create a trigger because I have a amazonbi account so this future, ones it was approved from this ticket https://quick-intake.harmony.a2z.com/request/V2038578192. was activated automatically and my flow was running without any approvals. is there a sitting in the amazonbi account that I should look for to find this “run with no confirmation” since it was not there during trigger set up?
Hi @Mohamed_Anwer,
Since this is an internal AmazonBI account, I believe this is outside what the public community can troubleshoot. I would suggest reaching out internally within your organization to see if they can provide some assistance. And if that doesn’t seem to work, I would recommend opening up a support ticket like I mentioned before Case management - AWS Support.