search

microsoft / coe-starter-kit

Other
727 stars 212 forks source link

[CoE Starter Kit - BUG] Unable to act on orphaned resources via Teams notification #7008

Closed KRhoadesHyp closed 8 months ago

KRhoadesHyp commented 8 months ago

Does this bug already exist in our backlog?

Describe the issue

I doubt this is a bug since no one else has reported it. We have a manager (a global admin) who has been receiving notifications from the Orphaned resources process since we enabled it, I believe it is for 3 different makers, a few dozen resources. He has not been able to Reassign or take ownership of any of them using the links in the Teams adaptive card, they just timeout or eventually come back with an error. In digging through the 'Request Orphaned Objects Reassigned (Child)' runs I found this error, undoubtable there are others - image

I am attaching the full text in the hopes you can tell me where to start looking? I am looking for other managers to see if they have had better luck reassigning.

error.txt

Expected Behavior

No response

What solution are you experiencing the issue with?

Governance

What solution version are you using?

October, 2023

What app or flow are you having the issue with?

Orphaned Resources

What method are you using to get inventory and telemetry?

Cloud flows

Steps To Reproduce

No response

Anything else?

No response

AB#620

Jenefer-Monroe commented 8 months ago

It sounds like the connection is broken. Please browse to connections in the environment as the user that setup the kit and repair any broken connections image

KRhoadesHyp commented 8 months ago

Okay, I did see the Teams connector had an issue. I will need to wait for the flows to re-run.

KRhoadesHyp commented 8 months ago

Will the change ownership buttons in the adaptive cards work on flows that are in solutions? If not do they return a specific error or just a general failure?

Jenefer-Monroe commented 8 months ago

I believe that this works yes. And we do return specific error messages when something fails to the user.

Jenefer-Monroe commented 8 months ago

Closing out as no further action for starter kit team

KRhoadesHyp commented 8 months ago

In case anyone else runs into this, the errors were due to a Forms connection inside of the referenced flows. The form belonged to a user who's account had been deleted.