Unanswered

Trigger Didn't Fire, But it Should Have

(1) Share

Report

Posted on by GD-16081559-0

I have 2 flows with triggers that are the same when a new email arrives. Both Flows should run based on the same email arriving.

1 flow is supposed to forward the email to me. It worked yesterday.

The other flow with the same trigger worked correctly. The only difference in "Code View" is the successful one has "Metadata", although they both worked yesterday. No changes made.

Why would the trigger not fire today ?

Combined with yesterday's problem, and various "quirks" in flows and running tests, I feel like PA is just not reliable or stable.

SUCCESSFUL TRIGGER on Flow #1

TRIGGER That Didn't Fire on Flow #2 (Both Triggers Fired yesterday, no code changes)

Categories:

General topics

I have the same question (0)

All responses (4)

Answers (0)

Sort by

David_MA 14,605 Super User 2026 Season 1 on at

Like (0)

Report
Copy link

Link copied!

Can you show the trigger condition of both flows as well as how the trigger is configured in both flows. There is probably some difference between the two that you are not noticing.

Although I am a bit confused why you need two flows that have the same trigger conditions and are supposed to run on the same e-mail. Why can't you do all of what you need to do in one flow?

Was this reply helpful? Yes No
GD-16081559-0 38 on at

Like (0)

Report
Copy link

Link copied!

These are the 2 triggers, also posted in the main post in "Code View". They both triggered yesterday when an email arrived, but only 1 triggered today, Both have the same Parameters.

The reason there are 2 flows, is because the main flow could not be modified at the time, so I made a 2nd flow. I now have access to the main flow and will merge the steps into the main flow, and turn off the 2nd flow.

Was this reply helpful? Yes No
David_MA 14,605 Super User 2026 Season 1 on at

Like (0)

Report
Copy link

Link copied!

When you mentioned triggers, I thought you were referring to trigger conditions. But with the images you provided, I see you are using the new designer. There are numerous issues with the new designer and Microsoft is supposed to be rolling out an update this month that is supposed to address many of the issues.

The issue you are having could be due to the fact you used the new designer to create the flow. I would suggest switching back to the classic designer and create your workflow over to see if that resolve the problem.

Was this reply helpful? Yes No
GD-16081559-0 38 on at

Like (1)

Report
Copy link

Link copied!

David_MA , the main flow needed the new designer, to get around a bug in the classic designer. I have since merged the 2 flows into 1, so I hope everything works normally going forward, and that new designer gets fixed !

Was this reply helpful? Yes No