Power Platform Community Forum Thread Details

Hi all

Thanks in advance for your help, I'm building a flow where the trigger is when an item or file is modified.

I want to build a trigger condition so it doesn't loop. The first is that the modified date is equal or greater than today.

The second is the "Status" value should be equal to "Completed". This is what I have so far but is not triggering the flow.

Date modified equal or greater than today:

@and(equals(triggerOutputs()?['body/Modified'], formatDateTime(utcNow(),'mm-dd-yyyy')), greater(triggerOutputs()?['body/Modified'], formatDateTime(utcNow(),'mm-dd-yyyy')))

Status value equal to "Completed"

@equals(triggerOutputs()?['body/Status/Value'], 'Completed')

Thanks!!

Categories:

Building flows

This issue with your trigger condition is that both of your statements have to be true for the flow to trigger. The modified date stores a time as well. Your first statement will never be true unless you format the modified date so it's only evaluating the date and not the time as well.

However, in your case, I believe that you only need a single trigger condition:

@equals(triggerOutputs()?['body/Status/Value'], 'Completed')

As soon as your item has been changed to Completed. It should trigger your flow. I don't think the modified date is necessary — unless I'm missing something? Any time you make a change to a SP item, it'll log the current date and time. So the first trigger condition statement isn't actually necessary.

You might be interested in this YT Tutorial:

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