Sharepoint listitem created/modified trigger occasionally getting skipped

[Anonymous]

I have two team flows that is connected to the same SharePoint Online list.

One triggers when an SP item is created and the other when an item is updated.

Ok, so the problem is that sometimes these triggers doesn't fire. According to the flow logs they have not even tried to run.

It seems at random but it feels like it happens during "heavy" load (when a couple of users are interacting with the list).

I need the triggers to actually fire every time (doesn't matter if it's 2 hours later), not to skip every now and then.

Anobody else experiencing the same problem? 

[gamoraes]

Hi mortez, thanks to post.

How plan/price of Flow you're using? You can find this page in the flow home page footer

[Anonymous]

Sorry, forgot to hand that information. I'm on a e3 developer license.

[Anonymous]

I'm having this exact same issue. I had an existing flow that was working at 100%, then I introduced a second flow. Since then, the first has only worked at about 64%. I deleted the second flow, and the first is still all sorts of bad. 

[v-micsh-msft]

Hi all,

We have received several feedbacks talking about this issue.

And our team has already submitted it to the Product Team from our side.

If there are any updates, I will post back.

Regards,

Michael

[Anonymous]

Thank you Michael.

Regards,

Linus

[v-micsh-msft · Accepted solution]

Hi All,

I got a response tolding that there are issues found for the SharePoint Modified trigger, and the fix is on the way, ETA is the end of this week.

Please update this thread if issue still insists next week.

Regards,

Michael

[Anonymous]

Thank you!

[Anonymous]

I'm with this issue. Every Time I create a new item on sharepoint, the email action is skipped. It only works if the creater is me.

Any update for this thread?

[RobLinstrum]

Hi - just seeing this post now, and am having this issue myself. The flow triggers about 95% of the time. When it does run, it runs perfectly. It's just totally unacceptable to have any margin of error. I am using the "When an item is created or modified."

Any updates on this issue?

Thanks