[CoE Starter Kit - BUG] Admin | Sync Template v3 (Driver) -> Admin | Sync Template v4 (Flows) / v4 (Apps) /v3 (Connection Identities)

[Rajeshgn053]

Does this bug already exist in our backlog?

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

Describe the issue

Note - This issue is related to #6451 & #6545. We want the fix recommended from our research to be implemented on COE next releases. Hence, raising it as new & requesting to get this fix applied on next releases.

1. “Admin | Sync Template v3 (Driver)” flow will trigger every day. Gets all the environments & loops them to Sync “Environments” table (Let’s say started at 9AM EST).

2. Prod tenant has ~3650 environments, which is taking total time of ~13 hrs (Ends at 10PM EST) to complete rest of the logic.
   Note- ‘DelayInventory’ environment variable is set to “No”

3. An environment that is placed at ~3156 iteration position, gets deleted ~11AM EST

4. By the time the iteration picks this environment (~7pm EST), logic just checks the dataverse table properties & proceeds updating the respective “Environments” row.

5. This leads in triggering the related sync flows & finally leading to the above errors.

• Admin | Sync Template v4 (Apps)
Action – Get_Apps_as_Admin
Error - "The environment '' could not be found"

• Admin | Sync Template v4 (Flows)
Action – List Flows as Admin (V2)
Error - "You are not permitted to make flows in this [environment GUID]"

• Admin | Sync Template v3 (Connection Identities)
Action – Get_Connections_as_Admin
Error - "The environment '' could not be found"

Please check our solution in Expected behavior section****

It should check the Environment existence, before performing next actions on each iteration.

Expected Behavior

Solution – For each iteration, before checking the dataverse properties, just check the environment exists or not (via Get Environment as Admin action), followed by Parallel branch operation.

If the respective environment is deleted by that time, an error occurs & empty scope branch action will be triggered, ending the respective iteration wit compose step (This step to avoid Flow run failure status, in negative case).
Then next in iteration will trigger.

This set of actions will take care of any Environment that gets deleted, after the loop starts.

What solution are you experiencing the issue with?

Core

What solution version are you using?

4.8

What app or flow are you having the issue with?

Admin | Sync Template v3 (Driver)

What method are you using to get inventory and telemetry?

Cloud flows

Steps To Reproduce

No response

Anything else?

The provided fix is tested, Please apply this fix in nex COE releases

AB#1388

[Jenefer-Monroe]

We can consider this change although we havent seen this be a big problem for users. Let me see what the API impact would be and let you know.

[Jenefer-Monroe]

Added a try catch like this.

[michael-wright-pwc]

Thank you @Jenefer-Monroe! (I work with @Rajeshgn053). This is much appreciated.

[Jenefer-Monroe]

You guys earned with your great debugging :)

[CoEStarterKitBot]

@Rajeshgn053 This has been fixed in the latest release. Please install the latest version of the toolkit following the instructions for installing updates. Note that if you do not remove the unmanaged layers as described there you will not receive updates from us.