Hello,
This issue often occurs when your flow includes connectors such as SharePoint or Outlook. To address it, start by setting the "Run only users" option to use the flow owner’s connections.
If that doesn’t solve the problem, the best workaround is to create a child flow and move those connectors into it. Then, configure the run-only settings of the child flow to also use the flow owner’s connections.
Cheers! 🎉
Ajlan
4
Fubar
2
Super User 2025 Season 1
CBDEV
2