My flow doesn't trigger when it should

(1) Share

Report

Posted on by PauloMaia

Hi.
I built a simple flow which checks every time an Azure Devops Work Item is updated.

There isn't any condition configured, and the only advanced parameters it checks is:

1.the type, which needs to be "Bug"

2. the area path comparison and iteration path comparison, which needs to be "Equals", and I can't remove these parameters, they always come back when I try.

When I monitor all bugs being updated and compare with the activities triggered of my flow, it doesn't match, there are a few work items that aren't triggering my flow.

How can I fix that?

Categories:

General topics

I have the same question (0)

All responses (2)

Answers (0)

Sort by

sandeepstw 312 Moderator on at

Like (0)

Report
Copy link

Link copied!

Hi @PauloMaia ,

To ensure your flow triggers for all updated bugs in Azure DevOps, do like this -

Make sure the trigger condition for the 'Bug' type is correctly set up.

The condition should be something like @equals(triggerBody()?['System.WorkItemType'], 'Bug').

Make sure the connection used in the flow has the necessary permissions to access all work items in Azure DevOps.

If you're using a webhook to trigger the flow, verify that it's configured correctly to listen to updates for all bugs.

Mark as solution if it helps.

Thanks,

Sandeep Mishra

Was this reply helpful? Yes No
PauloMaia 2 on at

Like (0)

Report
Copy link

Link copied!

Hi @sandeepstw !
Unfortunely this is what I did already.

As you can see, I think it's all set rightfully.
And the connection are all good too:

I still can't get what's missing. 😞

Was this reply helpful? Yes No