@nassetc The error you are getting is cause the values used in your condition don't match. 'Null' as you've entered is a string. However, if you want to check whether your Contract# column is not empty you should use the is not equal to operator and leave the second value field empty. I've linked a tutorial below for more troubleshooting tips.
Also, since you are using an automated trigger, I would recommend utilizing Trigger Conditions in your flow. This way your flow will only trigger when you want it to. In your case if the Contract # isn't empty. To learn more about Trigger Conditions, refer to the other tutorial I've linked below.
5 Power Automate Troubleshooting FAQs and Helpful Tips for Creating Better Flows
In this Power Automate tutorial, I explore 5 frequently asked questions that pop up when troubleshooting a flow. If you’d like to to level up your Power Automate flow skills and learn how to troubleshoot your Power Automate flow—this tutorial is for you!
IN THIS VIDEO:
✅ How to troubleshoot a false Condition action result
✅ How to get dynamic content when it isn’t selectable from the list of dynamic content
✅ How to troubleshoot an Apply to Each action that isn’t looping through
✅ How to troubleshoot a skipped Apply to Each action
✅ How to troubleshoot a Filter Query
✅ How to use a SharePoint yes/no column in a Filter Query
✅ How to use Compose actions to troubleshoot a Power Automate flow
✅ How to troubleshoot multiple emails being sent
✅ How to troubleshoot multiple Teams messages being sent
---
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
Hope this helps!
If I helped you solve your problem—please mark my post as a solution
✅.
Consider giving me a
👍 if you liked my response!
👉 Level up your Power Automate skills by checking out my tutorials on
YouTube👉 Tips and Tricks on
TikTok and
Instagram
Share
Report
12
All responses (
Answers (
