[CoE Starter Kit - QUESTION] Inventory Active Environments

[ClaudiuVio]

What is your question?

Since the last update, I can see in COE that I have only 275 flows in the default environment, but in the admin centre, I have 1476 flows.

I have extracted the list of all flows using PowerShell and the correct number is 1476

What solution are you experiencing the issue with?

Core

What solution version are you using?

April 2023

What app or flow are you having the issue with?

Admin - Sync Template v3

[ClaudiuVio]

The number of Apps is not impacted.

[manuelap-msft]

Can you check if the Admin - Sync Template v3 (Flows) is failing? You can do that by opening the CoE Admin Command Center app and checking the Sync Flows page for any failures.

[ClaudiuVio]

Nope, everything is OK.

The last failed sync flow was [Child] Admin | Sync Logs when the update was done.

[Jenefer-Monroe]

Can you please check on the value for this env var?

[ClaudiuVio]

It's not in use.

[Jenefer-Monroe]

You will need to find a repro of this in your tenant to see what is going wrong.

1. Find an environment in your tenant where you expect to see the object (ex this app missing, that chatbot missing, etc)

• Looks like you already have one here, the default envt

2. Go to the Power Platform Admin view app and find that environment. Open the record, edit some field, and save
   Note you will want to change back so be aware of the change.
   

3. This will trigger all the object flows to run for that environment. Find the flow for your object of interest and open it to details page.
   Ex: if you are looking for missing canvas apps chose Admin | Sync Template v3 (Apps)
   

4. Click on the timestamp of run in progress (or the one that just finished) to see the run itself.
   

5. From here you can explore if there is a failure, or if a bad return set, etc. And let us know if you have questions

[ClaudiuVio]

I did this, and now the syncs are running. I am waiting now to see if the flows are added back.

[ClaudiuVio]

The exact 3 runs that started after the actions requested failed.

Message error:

NOTE: All the other runs that started after this are successful.

[ClaudiuVio]

This issue occurs only on the Default env, for the others environments number of the flows is correct.

[Jenefer-Monroe]

Please note that failures like this "flow does not exist" are caught/expected failures. You will need to open the flow run and find the terminating failure

The first failure that is giving the message:
We use these calls to see if the object is new to the inventory, and if it is, this call to “get it” will fail. This failure is caught and the “isnew” variable is set to true.

Please find terminating failure:
In order to debug you need to find the terminating failure in the flow. Here for example the call to “forced failure” failed, and was not caught, so the flow terminated here. That is the spot you need to find in your failure in order to debug.