[CoE Starter Kit - BUG] Core Component 4.50.6 Update Fails

[cmd-k33n]

Does this bug already exist in our backlog?

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

Describe the issue

When importing the October release Core Components 4.50.6. The update import consistently fails with error:

CanvasApp import: FAILURE: Code: TooManyRequests Message: Too many requests sent to a service.

We previously made several attempts to update from 4.50.1. And retried the next day to see if that would resolve a potential rate limit issue. Then we decided to first update to 4.50.4 which succeeded on the first attempt.

Now attempting to update from 4.50.4 to 4.50.6 fails with the same error as before.

Expected Behavior

A successful upgrade to 4.50.6

What solution are you experiencing the issue with?

Core

What solution version are you using?

4.50.6

What app or flow are you having the issue with?

Core Components Update

What method are you using to get inventory and telemetry?

Cloud flows

Steps To Reproduce

Importing solution as per https://learn.microsoft.com/en-us/power-platform/guidance/coe/after-setup#import-the-new-solution-version

Anything else?

Since the update to 4.50.4 did not fail I assume it is not a rate-limit issue as suggested on previously reported issues with a similar error but something else.

Center of Excellence - Core Components_import.xml

[AmarSaiRam]

Hi, @cmd-k33n

1. Clean Import Environment
   Disable Background Flows: Temporarily turn off flows and apps in the environment (especially those related to CoE) to reduce concurrent requests.
   Clear Pending Solution Imports: Make sure there are no pending/unfinished solution imports in the environment.
2. Check Package Integrity
   Download the 4.50.6 Solution Again: Ensure the package isn't corrupted.
   Check for Known Issues: Review the CoE Starter Kit release notes and Issues page for related reports.
3. Retry Import with Increased Wait Times
   Wait Between Attempts: After a failure, wait at least 1–2 hours before retrying.
   Import During Off-Peak Hours: Try importing outside of business hours.
4. Incremental Import
   Import Apps/Flows Individually: If possible, extract the CanvasApp and import it separately.
   Split Solution: If the solution contains multiple apps, try importing them in smaller batches.
5. Raise Service Limits
   Contact Microsoft Support: If the problem persists, request a temporary increase in service limits for your environment.
6. Check Dependencies
   Validate Prerequisites: Ensure all dependencies for 4.50.6 are present and correctly configured.
7. Review and Attach Logs
   Detailed Import Logs: Download and review the full import log for specific components causing the error.
   Attach Logs to Issue: Provide these logs if escalating to Microsoft support.

[jesusfer]

I can reproduce this also in an EU environment when upgrading from 4.43 to 4.50.6. The System Jobs entry for the failure doesn't really say anything else than the error message above (CanvasApp import: FAILURE: Code: TooManyRequests Message: Too many requests sent to a service.)

[cmd-k33n]

Hi, @cmd-k33n

1. Clean Import Environment
   Disable Background Flows: Temporarily turn off flows and apps in the environment (especially those related to CoE) to reduce concurrent requests.
   Clear Pending Solution Imports: Make sure there are no pending/unfinished solution imports in the environment.
2. Check Package Integrity
   Download the 4.50.6 Solution Again: Ensure the package isn't corrupted.
   Check for Known Issues: Review the CoE Starter Kit release notes and Issues page for related reports.
3. Retry Import with Increased Wait Times
   Wait Between Attempts: After a failure, wait at least 1–2 hours before retrying.
   Import During Off-Peak Hours: Try importing outside of business hours.
4. Incremental Import
   Import Apps/Flows Individually: If possible, extract the CanvasApp and import it separately.
   Split Solution: If the solution contains multiple apps, try importing them in smaller batches.
5. Raise Service Limits
   Contact Microsoft Support: If the problem persists, request a temporary increase in service limits for your environment.
6. Check Dependencies
   Validate Prerequisites: Ensure all dependencies for 4.50.6 are present and correctly configured.
7. Review and Attach Logs
   Detailed Import Logs: Download and review the full import log for specific components causing the error.
   Attach Logs to Issue: Provide these logs if escalating to Microsoft support.

Hi @AmarSaiRam,

Thank you for your reply and suggestions. Allow me to respond:

1. I would have to try switching off all flows first. As you'll be able to tell from the print screens I've provided there are no other current actions or running imports. And I'd note that wasn't necessary in the past and also the current solution is running in a dedicated environment that is not generating any other errors of this kind.
2. Done. Also tried the September release as an intermediate and was able to upgrade to it successfully, but yet cannot continue to the October release. There are no other issues reported for this error.
3. Done. Please check this on the printsceens I provided.
4. Not sure how to do this, is there a guide I could follow?
5. In my previous experience hitting the Rate Limit prompts relevant alerts indicating that is the case and we have not received any such messages/email from the service. The only thing that's failing for us is importing this solution.
6. Which dependencies?
7. Logs had already been attached for your review.

With the above in mind do you maybe have any other specific suggestions to solve this issue?

Thanks in advance!

[Fabien-M]

HEllo, same error Solution "Center of Excellence - Core Components" failed to import: ImportAsHolding failed with exception :CanvasApp import: FAILURE: Code: TooManyRequests Message: Too many requests sent to a service. Client Request Id: xxxxxxxx, when trying to update to CoE 4.50.4.

[Nicosiajl]

Hi, I’m experiencing the exact same issue when trying to import the Center of Excellence - Core Components solution.

Currently deployed version: 4.50.2
Tested import versions:

• 4.50.3
• 4.50.4
• 4.50.6

Error message:
CanvasApp import: FAILURE: Code: TooManyRequests Message: Too many requests sent to a service. Client Request Id: e6dad85d-2f1a-4da7-bfd1-7b3b63835b85

To rule out version-specific issues, I’ve tested multiple releases with the same result.
I’d also like to highlight that no other solution fails to import in this environment, and the organization using this solution is a corporate-level tenant, which may be relevant in terms of service limits or throttling.
Any insights or workarounds would be greatly appreciated.

Thanks in advance!

[AmarSaiRam]

Wait & Retry with Cooldown:
Although you already tried on different days, some tenant-level or environment-level throttling can persist for hours to days, especially after bulk actions. Ensure no parallel imports or automated processes interact with Power Platform at the same time.

Import During Off-Peak Hours:
Try the import during known lower activity periods (outside normal business hours), as throttling can be affected by global tenant traffic.

Slice Import if Possible:
If your solution has multiple managed layers or apps, attempt to split them and import incrementally, starting with base components, then apps. However, the Core Component solution may not support modular imports.

Raise to Microsoft Support:
As this error persists across versions and environments, it’s possible your tenant has hit some undocumented limits or is affected by a fresh throttling rule. Open a ticket with Microsoft, referencing error code 80072352 and the Client Request Id in your screenshot for faster triage.

Review Tenant Service Limits:
In large organizations, service quotas or throttling policies may be set by your IT or Power Platform admin. If possible, have them review the API and service limit dashboard (in Power Platform Admin Center: https://admin.powerplatform.microsoft.com/) for any anomalies.

Telemetry and Verbose Logs:
If you haven’t already, enable detailed logging on import and check for related failures in DLP, plug-ins, or connector runs that might contribute to overall request count.

Check for Pending Solution Updates:
Occasionally, stuck or pending solution operations can cause repeated service calls. Confirm that there are no “locked” background solution imports or updates lingering.

[jesusfer]

In the end, we just waited and two days after the solution was deployed successfully.