Regarding the two stage process, unfortunately no. If the survey never hits Power Automate, then there isn't much to be done. This one troubles me as well, but luckily it doesn't seem to be very common (I think I've only gotten one complaint in the last 6 months - and that's out of thousands of surveys).
The two-stage process protects mainly against two things:
- SharePoint glitches. From time to time, I've seen SharePoint do some random things, such as items not getting entered into lists for instance; and
- Esri report generation glitches (both small and large). This one seems more common. Sometimes the report generation service just doesn't want to work first try, but second try it runs flawlessly. I am also protected against large service outages and bugs in the report generation service. While this is more rare, it's happened three times that I can remember in the last couple years, and each time I just had to tell people "reports will be delivered soon. Just keep submitting like normal". Other than Feature Reports being a day or so late, I didn't have to change a thing on my end to get those reports delivered.
There are a few other miscellaneous things it covers against, but I am thinking that they are more corporate-environment specific, such as missing corporate emails when our IT doesn't add someone to the proper user group (rare, but it has happened). Overall, I've found the two-stage process it to be very self-sufficient.
The biggest hurdle I have right now is users ignoring approvals and letting things timeout. The timeout itself is covered by the error handling, it's more that people aren't doing what they should be! 😂 On a side note, for anyone using approvals in Power Automate, there IS a way around the 30-day limit of Microsoft approvals now. I feel like this isn't well enough known at the moment.