[CoE Starter Kit - BUG] ISSUE TITLE

[RegassaKedir]

Does this bug already exist in our backlog?

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

Describe the issue

During the upgrade of the COE from Core Components 4.50.2 to CenterofExcellenceCoreComponents_4.50.6, I keep encountering the following error:

"Solution 'Center of Excellence - Core Components' failed to import: ImportAsHolding failed with exception: Error while importing workflow {1edb4715-b85b-ed11-9561-0022480819d7} type ModernFlow name HELPER - Add User to Security Role. Flow server error returned with status code 'BadGateway' and details.".

Expected Behavior

No response

What solution are you experiencing the issue with?

Core

What solution version are you using?

Center of Excellence - Core Components 4.50.2

What app or flow are you having the issue with?

Upgrading to the latest coe version

What method are you using to get inventory and telemetry?

Cloud flows

Steps To Reproduce

Anything else?

No response

[RegassaKedir]

[harini-2-y]

Hi @RegassaKedir,
Thanks for raising this issue.

You are seeing a BadGateway (HTTP 502) error during the upgrade because the Power Automate backend service was temporarily unavailable while importing the flow “HELPER – Add User to Security Role.”
This is a transient Power Platform service issue, not a problem with the CoE Starter Kit or your environment. The existing data and components remain safe.
How to Resolve It
Please try the following steps:
Wait 30–60 minutes and retry the import using the Upgrade option.
This resolves most 502 errors because the service becomes available again.
If it still fails, retry during off‑peak hours
(early morning or late evening), when the backend load is lower.
Check Microsoft Service Health to ensure there are no active Power Platform / Power Automate incidents before retrying.
No other changes are required

You do not need to modify flows, connections, or permissions.
This error is temporary and the import will succeed once the backend service recovers.

[harini-2-y]

Hi @RegassaKedir,
We haven’t heard back in a while, so we’ll proceed to close this issue for now. If the issue persists or you need further assistance, feel free to log a new issue. We’re happy to help anytime. Thanks again for your engagement!