No error, did not run

[EricDesignTech]

Is it possible that a flow can have errors and not run? I'm trying to troubleshoot, but I can't tell if it's not producing "runs" because there's an error. I have no idea how to troubleshoot since there seems to be no way to view errors. 

[EricDesignTech]

Looks like it needs to be running correctly before it produces an error, also it won't even qualify a run with an error as a run. I'm used to errors being helpful when it's not working but if it's initialized it should be considered a run and show errors. Man I hate MS.

Also "key value" in Excel is the "row". Wish the UI said "row" -- that would have saved me several hours. 

[EricDesignTech]

NOT SOLVED, spoke too soon, changing it to writing to row 2 in Excel makes it so PA no longer runs, row 1 runs but produces an error because it's a table heading. row 2 ("key value" 2), which is correct, fails to run and failed to produce an error or anything useful in troubleshooting

[v-liwei-msft]

Hi @EricDesignTech ,

Could you please provide me with detailed screenshots of the flow that is bothering you?

Best Regards,

Levi

[EricDesignTech]

It appears what causes it not to run is bug in Power Automate -- or just bad semantics, which is more in-line with MS product design.

The PA command for Teams called "When a new channel message is added" does not initiate an action for any message, it only initiates when a new *conversation* is added, and not when replies to a conversation are added. The name of the command is ambiguous and confusing. This theme in MS products is why I'm trying to get the information outside the MS ecosystem as soon as possible so I can script the automation like a pro. 

[GuyBoswell]

None of my flows have been running properly for hours.  Suspect Microsoft are doing something behind the scenes.  It not us, its them!