One flow triggering another flow problem

[BlackMamba]

Hi everyone 🙂

I have two separate automated workflows in place.

1. The first workflow is initiated manually by a user. It retrieves an item from a SharePoint list, creates a corresponding work item in Azure DevOps, retrieves the generated AzureDevopsID, updates the SharePoint item with this ID, retrieves attachments, and attaches them to the created work item in Azure DevOps.

2. The second workflow is triggered automatically whenever an item or file is modified in the SharePoint list. It retrieves the modified item, updates the corresponding work item in Azure DevOps, and attaches any updated attachments to it.

However, I'm encountering an issue where the first workflow's action of updating the SharePoint item with the AzureDevopsID triggers the second workflow, which I want to avoid. I need to prevent the first workflow from inadvertently triggering the second one when updating the SharePoint item with the AzureDevopsID. How can I accomplish this?

1. 

[creativeopinion]

@BlackMamba For the flow that uses the When an item or file is modified trigger, you could use a Trigger Condition to prevent it from triggering unnecessarily. For example, if you have a status column in your list you could set your flow to only trigger if Status is equal to a specific value. This is just an example. Depending on your needs and workflow you may need to adjust. Alternatively, you can also have your first flow run from a service account. In your second flow, you can set the trigger condition to only fire if the item isn't updated by the service account.

You might find this YT Tutorial helpful: 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. IIf 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

[BlackMamba]

But I would like it to trigger when user changes one of columns ex. Status, Priority, Assigned To or adds and attachement. 

[creativeopinion]

@BlackMamba I understand that. You'll need to figure out the logic to prevent it from triggering when you don't what it to trigger. I'm not exactly sure what that logic is. All I can understand is that you don't want it to trigger when the first flow runs. However, the first flow ends with an Update Item action—this will trigger your second flow.

As mentioned before, you have to work in logic to prevent it from triggering your second flow when you don't want it to. It could be another column you add to your list that you use to mark your item after your first flow is complete. Let me know if you need further clarification.