The files could vary from 50 MB to multiple GB. A delay trigger won't really work for my scenario, unfortunately, but thanks for the suggestion.
I've been trying to move files on a created trigger for testing/POC purposes, but that's not really my goal. I'll do my best to outline my scenario, but note that it's a bit complicated.
Here's my scenario: I have a PowerApps interface where users can upload files using the attachment control and then clicking a button, which uses the PowerApps v2 connector to upload those files to a Document Library. This works great for files up to 50 MB, beyond which I need an alternative solution. My original idea was adding a link to open a "Upload Queue" Library in a separate tab, which would be configured to only show the user's own files, where they could 1) upload their large files, 2) tab back to PowerApps, 3) click the upload button which would now both upload the <50 MB files from the attachment control and migrate any files they have in the "Upload Queue" library to where they're meant to live, automatically tagging these files with various properties (as is required for my scenario).
This all works great, in principle, except that if they tab back and click that Upload button before one of their files have finished uploading. As such, I was hoping to configure my Flow (which triggers when they click that Upload button) to loop & delay until all of the files Created By the current user have finished uploading and then do the migration of those (in addition to uploading the files from the Attachment Control), noting that my PowerApps interface is waiting for a callback before proceeding to another screen. It may be worth noting that all of the files must be uploaded before proceeding to that next screen, because there's a Gallery of all context-relevant files from the Library on that next screen which they can then tag with various additional properties.
The delay would work so-far as I'd have to force my users to wait 5-10 minutes before proceeding (allowing for files of multiple GB), even if they only uploaded a few hundred MBs worth of files, which unfortunately isn't an acceptable UX for my scenario.
If there was some way for my Power Automate flow to check if the files retrieved via the Get Files action were fully uploaded (in a loop + delay structure, that keeps checking until they're all fully uploaded and then moves on), then everything would work great, but it seems like that may not be an option?
As of now, my alternative solution is to have my users upload their large files directly to the end-destination Library (instead of the "Upload Queue") with some added complexities, which might suffice but is far from ideal for various logistical reasons.
