[CoE Starter Kit - BUG] Env Request | Cleanup : Failed to delete an environnement

[tocri]

Does this bug already exist in our backlog?

• I have checked and confirm this is a new bug.

Describe the issue

Hello

I have an environment that was created by user and the expiration date is outdated. each day, the flow gives me this error :

"The delete reason was null or invalid. Valid values are: User, Tenant, Expiration, LinkedResourceDeleted, Manual, CommonDataServiceMigration, Application, Service, TeamDeleted, ConnectedGroupDeleted, CreateFailed, InactivityThreshold, DeletedByTenantPolicyEvaluation, InconsistencyDetection"

the initial request :

Any idea ? How can i help you ?

Expected Behavior

No response

What solution are you experiencing the issue with?

Core

What solution version are you using?

4.33

What app or flow are you having the issue with?

Env Request | Cleanup

What method are you using to get inventory and telemetry?

None

Steps To Reproduce

No response

Anything else?

No response

[Jenefer-Monroe]

It looks like the product changed what its expecting here. I tried a more current API Version and it did not fix unfortunately
Here is the error received: InvalidOrMissingDeleteCode

I'm afraid you'll need to contact product support and I'll also post something internally.

Before contacting product support please create a flow outside the context of the CoE. Its as simple as the only shown here.
Just the single action, select the envt, and have the API version of 2022-05-01 (although it also repros for more current versions)

[tocri]

Thank you. I have added this task to my bucket list for tomorrow. Thanks as usual for your quick reply.

[tocri]

If I add the delete environment action, the API version is 2018-10-01 and if I try to delete an environment, it says "not found" after a few seconds but in fact the action does delete the environment with this version of the API.

I tried 2 times and each times the environment is deleted.

[Jenefer-Monroe]

Thanks yes we used to use that version but bumped it forward at the product teams request, I dont recall why.
I've created an internal incident too but your customer report will help bump it in priority.

[tocri]

Ok but what can i say to the support team. "The flow env Requsest | cleanup" doesn't work because the API that is use for deleting an environment is buggy ? " Are they going to tell me to see this with you?

[Jenefer-Monroe]

Before contacting product support please create a flow outside the context of the CoE. Its as simple as the one shown here.
Just the single action, select the envt, and have the API version of 2022-05-01 (although it also repros for more current versions as well)

[tocri]

Sorry for the delay. A lot of work since the holidays. As you thought, it doesn't work. I'll create the post in a few hours. Any recommendations that will be useful to the support team that you can provide me?

[tocri]

Ticket is created. Fingers crossed

[lsavard]

Hi, we are having the same issue. Any news about it ? Thanks.

[lsavard]

Looks like we have to submit a delete reason :

[tocri]

@lsavard @Jenefer-Monroe I've opened a ticket to Microsoft and an engineer is on this. She tried to contact @Jenefer-Monroe on teams without success but i think she is on vacation.

I'll keep you posted

[tocri]

Ok i've an answer :

"They have found this to be a bug which seems to be affecting API versions, and they have created an internal bug ticket to work on it. There is currently no ETA as to when the fix will be developed and deployed

In the meantime, they have suggested that you use the API version 2018-10-01 for now since the environment does get deleted using that API even though an error is thrown."

[rmedrano2]

@Grant-Archibald-MS @Jenefer-Monroe we started getting this error starting on December 20th in the Environment Cleanup daily flow. We are using a slightly older version of the CoE Starter Kit - Core V 4.37 - do we know if this was fixed in the later releases?