I'm having an issue with several flows firing twice on file creation. I'm using the on-premise gateway, and looking for a file to be created in a specific folder located on a local network NAS. Both executions fire within a few seconds of each other. If I look at the details for the first execution (screenshot marked '1' below), the body response is empty. On the second execution (screenshot marked '2' below), I see the expected file details appear. Any suggestions on what to try, as I've exhausted my google searches?
Here's what happens when I copy and paste a .txt file into the folder being monitored - '1' is first execution with seemingly no file, and '2' is the second execution with the file as expected. I can set up an exit condition if the trigger body is empty, but would rather fix the root cause if possible.

The file is not modified by the flow - only deleted - and the first execution actually skips this logic as there is no file to process:

Here's the trigger - not much for me to muck up here:

Things I've tried:
1) Changing the trigger to a new folder 'SanityCheck' that I know no other flows are using.
2) Deleting and re-creating the trigger action
3) Googling until my fingers bleed...
------------------------------
Jeff Woodard
Chief Technical Officer
Transportation Financial Services, Inc.
West Palm Beach FL
(561) 832-3110
------------------------------