You’re offline. This is a read only version of the page.
I am using an extremely simple PA flow that ingest emails from ANY sender with a subject containing a keyphrase and then it sends out an email.
The sender is always one of 3 different email addresses from our vendor, and they all flow into the same mailbox.
I have setup alerts for this agnostic sender flow, as well as explicit ones ONLY containing their specific email addresses.
Every time we get test emails from them (they send from all 3 addresses spaced out over 10 min) the agnostic sender flow randomly chooses 1 or 2 and processes, but does not for the others. For the explicit sender flows they also randomly run even though I am staring at nearly identical sets of 3 emails sitting in the inbox. What could possibly be causing this randomness and is there another methodology I could utilize to avoid this?
As a note I can send from my internal/personal email addresses and the flow ALWAYS catches them, it's only from our vendor this is occurring (2/3 addresses use subdomains btw).
Halpppp
@abusivetortoise Are you using Trigger Conditions in your flow trigger? If so, can you share a screenshot of what those look like? If not, I would suggest you add Trigger Conditions to your flow. This way your flow will only run if the conditions are met. It's especially helpful with something like the When a New Email Arrives (V3) trigger as this trigger must always trigger first, then run the check to see if the conditions match. With Trigger Conditions, the flow wont even run at all if the conditions don't match.
Also, another thing you can try as well is to switch to the Classic Designer and save your flow in the Classic Designer. The New Designer is still buggy.
Check out this YT Tutorial for more details on how to add Trigger Conditions to your flow: 4 Ways You Can Use Trigger Conditions in Your Microsoft Power Automate Flow
If you are using an Automated Cloud flow trigger in your flow—you need to consider adding trigger conditions.
Do YOU 🫵 know what a trigger condition is? Trigger conditions can be set in most flow triggers. These conditions you set must be true for the trigger to fire. In this Power Automate tutorial, I’m going to show you how to use trigger conditions in your flows to control when your Power Automate flows trigger.
If your plan has flow run limits—you can avoid triggering your flows unnecessarily by using trigger conditions.
I’ll cover four different flow examples that would benefit from trigger conditions:
⚡️ Triggering a flow when a column is changed to a specific value
⚡️ Triggering a Flow When an Event Updated or Deleted
⚡️ Triggering a Flow When a New Folder is Created
⚡️ Triggering a Flow When a Specific Email is Received I’ll also show you a trick on how to easily create the expressions needed and give you a few tips on how to troubleshoot your flow.
IN THIS VIDEO:
✅ Four different flows that would benefit from trigger conditions
✅ What is a trigger condition?
✅ How to add a trigger condition to your flow
✅ How to trigger a flow when a column is changed to a specific value
✅ How to trigger a flow when an event is updated or Deleted
✅ How to trigger a flow when a new folder is created
✅ How to trigger a flow when a specific email is received
✅ How to troubleshoot a trigger condition
✅ How to prevent case sensitivity issues with a trigger condition
✅ How to use the filter array action to easily compose an expression that can be used in a trigger condition
Share
Report
All responses (
Answers (
10,504
