I have seen this reported a few times, but it would be great to have it addressed and corrected. Especially as I am finding other issues with this trigger as well. The common issue is that if you create a blank flow using the "For a Selected File" trigger you can't get file properties easily as the File ID is not available in Dynamic content. There are two workarounds. Grab it in a compose or use the Create a custom action for a selected file template. While the workaround works, the user experience is not great.
I found another issue today. This is around the SQL connector. If any actions from a SQL connector are used in flow with this trigger the actions will fail. Errors usually are "Permission Exception. inner exception: Internal error: dataSourceCredentials" Using a SQL connector with the same connection in a flow with a different connector works just fine, but as soon as any SQL actions are added to a flow with this trigger the SQL actions no longer work.
Has anyone else encountered this?
