I indeed tried deleting the trigger action and adding it back into the flow.
I also tried a few times with a brand new form and a brand new flow, always using the same account. The creation works fine, but testing the flow fails.
Attached is one such example of a new flow, and as you can see it is as simple as it can be:
a) The flow should fire off as soon as a new response is submitted to a form called "JustSomething"
b) It then should send an e-mail.
The form "JustSomething" only asks to fill in a word, and when using it I can indeed see coming in the answers in Microsoft Forms.
However, the automated cloud flow is never fired: it doesn't 'see' the event happening, as if it has no connection to Forms (but it does have one and it's 'green').
Since the flow doesn't start at all, it also doesn't 'fail' with some kind of error message. There are no flow runs visible in the history log, it simply stays blank.
I created such flows multiple times in the past (with success), now I'm out of inspiration what could be the root cause of the issue.
When I create another type of cloud flow, e.g. one that fires off as soon as a new file arrives in OneDrive, it works perfectly well.
Only when I use a trigger that is related to Microsoft Forms ("When a new response is submitted"), the flow stays dead.
