The same problem occurs when a trigger comes back from a retry state...
Since we can configure "on error reconnect" parameters on a trigger, the trigger obviously knows when it's in a retry state...
Why not add a check box for "Fire trigger upon successful retry", that is fire the trigger when it switches from retry state to normal state. This would make the trigger catch up on files that were created during for example a communication issue.