You’re offline. This is a read only version of the page.
59
I realized that I have a flow that I use to save files (reports) I receive from a terminal application. (only way we can transfert from).
I was using it often in the past but didn't use in the last few months, so I didn't realize it wasn't working until it was turn off. I turning it back on but it doesn't work.
This is the trigger I am using : @equals(triggerOutputs()?['body/from'], 'myusername@rscXXX.tennant.com')
Nothing happens, the flow doesn't get trigger.
If I use the condition "from" in the step like this :
From: myusername@rscXXX.tennant.com
Include Attachments:Yes
Importance:Any
Only with attachments:Yes
Folder:Inbox
Then it works.
Did something change in power automate for triggers ? Or did I change something in the past without realizing I made a mistake ?
@Watever Could you share a screenshot of your flows? It would be helpful to look at.
I might have to create a brand new flow. I had it with the old design and doesn't work.
I have another flow (don,t remember if was created with new or old design) that works fine. I also create a copy of that one with the new designer and it works. So I don't know why that particular flow do not work.
@Watever Okay have you tried creating a brand new flow? If not, I'd recommend doing that and before you start editing your flow switch to the Classic Designer.
Run a test. It shouldn't matter if there is anything in the body as your flow should still trigger...
Yes it does have attachment. That,s actually the only thing it contains, nothing in the body etc...
It's weird that it was working in the past and it stopped working. I don't think that a new or classic designer change something once the flow is created. I believe that the new designer sometimes doesn't compile the same way, like the "null" is returned as and empty string "" instead of null type. Or the body subsection might not be interppreted the sameway. But otherwise, once "compiled" it's the same, no ?
@Watever It's part of the trigger. However, if you have it in the trigger (not as a trigger condition—set in the settings of the trigger) your flow will always trigger. The trigger condition will check first if the conditions are true before even triggering the flow. Hope I'm making sense.
Your flow trigger states that you only want to include emails with attachments. The tests you are running, does your email have attachments?
I tried it with the old designer and seems to do the samething.
If I have parameters in the first step/action trigger, doesn't it make it part of the trigger ? I am wondering. (I am not talking about using a condition step)
@Watever It looks like you are using the new designer. Have you tried editing your flow in the Classic Designer to see if that works? The new designer is still kinda buggy. If that doesn't work, you might need to create a new flow, switch to the Classic Designer first before editing your flow.
I'd also like to recommend that you use a trigger condition for your flow. Trigger conditions will prevent your flow from triggering unnecessarily. The way you currently have your flow set up means your flow will trigger every time a new email arrives and only continue on with the flow if the conditions you've set in your trigger are met.
However, with a trigger condition (or conditions) you can prevent your flow from even triggering in the first place.
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
#1
WarrenBelz
146,645
Most Valuable Professional
#2
RandyHayes
76,287
Super User 2024 Season 1
#3
Pstork1
65,997
Most Valuable Professional
Share
Report
All responses (
Answers (
