Flow with trigger "When a new email arrives (V3)" not firing

[gcoleman]

My use case is simple: notice when a new email arrives in a specific Outlook 365 mailbox, and contains a key phrase in the subject line, and has an attachment. The first version I created several days ago in my Sandbox environment seemed to work fine when I tested the flow a couple of times.

But now, coming back several days later, it will not trigger, and I can't think of anything else to check at this point. 

For a while, I was distracted by the status = off value for the connection reference. But apparently this is the expected status even for a working connection reference.

Since it's such a simple flow, I deleted the flow and associated connection references, and re-built it in a new minimalist version, but that still does not fire.

I thought maybe my Sandbox environment was somehow deficient, so I built a version in Production. But that does not fire either.

I wonder if the recent Office 365 password change I executed is creating a problem--but am hopeful that this should not have to be overcome manually somehow. (And creating and refreshing connection references seem to work without a hitch. And I have re-logged into makepowerapps with my updated creds.)

So I'm stumped and would appreciate any suggestions from the community. Thanks!

[happyume]

On the left navigation bar for your make.powerautomate.com page, go to Data -> Connections and see if there is a connection that has status like - "Can't Sign in. Fix Connection".  Once you fix that connection, your Flow should start working again.

Please click Accept as solution if my post helped you solve your issue. This will help others find it more readily. It also closes the item. If this post or my previous reply was useful in other ways, please consider giving it Thumbs Up.

[gcoleman · Accepted solution]

Thank you for your message @happyume ! I had not discovered before the view of connection references you mention. There were a couple of connection references in the state you anticipated, but not the one I was concerned with. But given your pointing to the connection reference as the potential source of the problem, I uncovered the issue: when I found the relevant connection reference in the solution browser and edited it, I found that it had no display name or name. So I filled in a display name and saved. (The name was then supplied by the system.) Now it works!