Power Automate flow isn't triggered "When an item is created"

[Greg27]

I am pretty new to Power Automate and I have a flow I created that is triggered "When an item is created". My Power App form writes a SharePoint List row, which should trigger the flow. However, I have created 2 rows in my SharePoint List and the flow hasn't started. It's been days and it still hasn't been triggered. Is there a way to determine why?

[jinivthakkar]

@Greg27 you can have a error logging mechanism like try catch in your flow, please see this 

https://www.youtube.com/watch?v=a6rGbJXsH1U

may be some condition is not met, are you your flow does not the flow have any trigger condition, please see this 

https://www.youtube.com/watch?v=tlS6pSAx-GY

--------------------------------------------------------------------------------

If this post helps answer your question, please click on “Accept as Solution” to help other members find it more quickly. If you thought this post was helpful, please give it a Thumbs Up.

[Greg27]

@jinivthakkar 

I am not seeing any errors and it tells me that my workflow is ready to go. My Workflow is triggered by a new item in my SharePoint list. The first step that it does is to email the person who created the list row. So, since I created the list row, it should email me, but it doesn't.

[jinivthakkar]

@Greg27 the other reason for the flow not triggering can be that the user does not have license for flow.

[Greg27]

@jinivthakkar 

I have created one Power App writing to a SharePoint List and a new item in that List triggers my Power Automate Flow. My new Power App does the same thing, but that Power App Flow is not working. I am running both and my first Flow works and my 2nd one doesn't. I have a license, but also everyone here has a license.

[Greg27 · Accepted solution]

@jinivthakkar 

I decided to finally create a 2nd flow that triggered "When an item is created", but this one only sends an email. The minute I added a new row in my SharePoint List, both flows were triggered. I have no idea why, but that was what happened. Not sure if there is some sort of bug or something else, but that tells me there was likely nothing wrong with the original flow.