cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
njhfmstr
Regular Visitor

Flow based on VSTS onworkitemcreatedv2 keeps triggering

I have a flow based on VSTS / Azure Devops "onworkitemcreatedv2", which simply posts me all Prio 1 Bugs into a Teams channel. All worked fine until today, it keeps firing, although the Bug is already done & closed. Any ideas?

8 REPLIES 8
v-yamao-msft
Community Support
Community Support

Hi @njhfmstr ,

 

Could you share a screen shot of your flow?

 

From your description, it seems that the flow keeps running and posting the bugs that already done into Teams.

 

I have made a simple test using the following flow. However, only when the Bug is created, the flow will be triggered.

1.PNG

 

If possible, please try creating a new flow to see if the issue still exists.

 

Best regards,

Mabel

 

Community Support Team _ Mabel Mao
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

Hey, 

it also worked fine for me until yesterday.

The only thing I made differently was, not creating a ticket from scratch but changing the type in Azure Devops into a Bug and then also cloned that one. And the clone keeps spamming / triggering the Flow, although it's already Done.

 

Screenshot 2019-05-21 at 09.07.39.png

@v-yamao-msft  I activated the flow again, and created a new clean ticket, and it keeps posting to Teams every second. Please advise.

We're having exactly the same problem since Friday, May 10th (flow was not changed and working perfectly the last 7 months) . We had to stop the flow. Tried to reactivate it again today, but still the same problem.

v-yamao-msft
Community Support
Community Support

Hi @njhfmstr , @thom ,

 

Thanks for updating.

 

If you create a new flow, will the issue still happen?

 

If the issue still exists, please share a URL to the flow’s run details, I will help involve more resources to look into this issue.

 

Best regards,

Mabel

 

Community Support Team _ Mabel Mao
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

@v-yamao-msft I recreated my flow from scratch as you suggested (identical flow) and for now it seems to be working correctly indeed. Do you know what caused this problem on my old flow?

@v-yamao-msft  i re-created the flows and it seems to work. what caused that issue?

Helpful resources

Announcements
Power Platform Conf 2022 768x460.jpg

Join us for Microsoft Power Platform Conference

The first Microsoft-sponsored Power Platform Conference is coming in September. 100+ speakers, 150+ sessions, and what's new and next for Power Platform.

New Ideas Forum MPA.jpg

A new place to submit your Ideas for Power Automate

Announcing a new way to share your feedback with the Power Automate Team.

MPA Virtual Workshop Carousel 768x460.png

Register for a Free Workshop

Learn to digitize and optimize business processes and connect all your applications to share data in real time.

Super User 2 - 2022 Congratulations 768x460.png

Welcome Super Users

The Super User program for 2022- Season 2 has kicked off!

Users online (2,821)