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!