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?
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.
If possible, please try creating a new flow to see if the issue still exists.
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.
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.
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.
@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?
Dive into the Power Platform stack with hands-on sessions and labs, virtually delivered to you by experts and community leaders.
Watch Nick Doelman's session from the 2020 Power Platform Community Conference on demand!
Check out the community blog page where you can find valuable learning material from community and product team members!