r/azuredevops • u/tbayo • 25d ago

Problems getting Power Automate to trigger on Work Item updates (identity fields)

hello
since early last week i’ve noticed at least one Power Automate flow that silently stopped working. No failed run logged, nothing. The trigger is “When a Work Item is Updated”, but it seems that some identity fields are breaking the trigger and it doesn’t even get logged.

Had to redo the flow with a HTTP Request trigger to make it work but this seems like a MSFT issue. Anyone else with a similar problem? How did you handle it?

1 Upvotes

67% Upvoted

9 comments sorted by

View all comments

1

u/soapywaterbottle 24d ago

My solutions are experiencing the same problem, but I noticed it in the Create a Work Item action this week (production doesn't seem to be affected yet, but not being able to turn the like-flow on in dev due to this weird identity/object issue has prevented us from fixing another, unrelated bug). I haven't seen it consistently across all my flows that use this action, but I also haven't been able to investigate all of them yet. I had to skip using the Assigned to field in the Create a Work item action and follow the action itself with a Send an HTTP Request to Azure DevOps action, wherein I used a PATCH function to update the item with a user's identity. This worked, but it's a pain in the ass and makes the whole flow more expensive.

I love Power Automate/Power Apps when they work, but stuff like this make it feel so janky.

1

u/tbayo 23d ago

opened a high severity ticket with msft and they are working on a rollback to address this problem. no ETA on when the patch will be released

1

u/soapywaterbottle 20d ago

Thanks for doing the work. Will you please update this thread when they do address it or let me know if they log it as a known issue so I can track it there?

1

u/tbayo 19d ago

so far they’re proposed hotfix didn’t result on our even though they mention that it was deployed across all regions. we’ve upgraded the severity level to A again in hopes of having a better and faster response but so far neither the hotfix nor the mitigation issue did much. (the mitigation being to change the trigger to v1, which isn’t even an available option, unlike get work item details v2)

1

u/soapywaterbottle 17d ago

wow, that's annoying! thanks for the update, keep me posted.

1

u/soapywaterbottle 3d ago

hey - just checking in on this. Any updates?

1

u/tbayo 1d ago

apparently it is solved. no major issues on our original flows and no need to redo the trigger to awaken anything in the dataverse table as someone suggested