Add comprehensive troubleshooting documentation for TooManyRequests errors during CoE Starter Kit upgrades#10702
Merged
harini-2-y merged 3 commits intomainfrom Jan 22, 2026
Conversation
…quests errors Co-authored-by: harini-2-y <235104376+harini-2-y@users.noreply.github.com>
Co-authored-by: harini-2-y <235104376+harini-2-y@users.noreply.github.com>
Copilot
AI
changed the title
[WIP] Fix Core Components upgrade error in CoE Starter Kit
Add comprehensive troubleshooting documentation for TooManyRequests errors during CoE Starter Kit upgrades
Jan 13, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Users upgrading CoE Starter Kit Core Components across large version gaps (e.g., 4.43 → 4.50.6) encounter
TooManyRequestserrors during solution import. This occurs when multiple Canvas Apps trigger Power Platform's service protection limits—not a bug, but a platform safeguard that requires specific mitigation strategies.Changes
New Documentation
TROUBLESHOOTING-UPGRADES.md(375 lines) with:Integration Points
README.mdwith Troubleshooting sectionKey Recommendations
Incremental upgrades resolve the issue by reducing Canvas App changes per import:
Critical: Import Core Components first, wait 30-60 min before subsequent solutions. If error occurs, wait 60-90 min before retry (2-4h optimal).
Original prompt
This section details on the original issue you should resolve
<issue_title>[CoE Starter Kit - BUG] ISSUE TITLE</issue_title>
<issue_description>### Does this bug already exist in our backlog?
Describe the issue
I opened a ticket with Microsoft support and they provided me with the second set of 5 troubleshooting steps below. They said if those did not work I would need to open a support request here.
I am attempting to update Power Platform CoE "Core Components" from version 4.43 to 4.50.6, but the process is failing with the 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: 09326ac8-58fb-4dec-b4d0-d0d4ed40c0d9."
Based on my research this is a known issue when upgrading CoE Starter Kit solutions (including Core Components) from 4.43 → 4.50.x. It happens because the import process sends multiple requests to the Canvas App service, hitting rate limits. Retry After Waiting Wait at least 30–60 minutes before retrying. Avoid running other imports or heavy operations during this time. Import During Off-Peak Hours Perform the upgrade when your tenant is less active (early morning or late evening). Use the classic Power Platform Console Attempted to use the classic console because I read it can be more stable for these upgrades. Change update version I was trying to upgrade from 4.43 to 4.50.6 (it's been 13 months since we've upgraded). Based on my research each upgrade contains many Canvas Apps which can result in the rate limit being reached. Instead of trying to import the newest latest upgrade I tried going to 4.47.1 with the thought that there would be less Canvas App. I performed the following troubleshooting step but the update continues to fail.
I have also tried these troubleshooting steps provided by Microsoft support but none of these worked:
Installing all components together can cause the version check to fail, so importing them individually helps avoid that.
Navigate to Power Apps Admin Center → Environment → Solutions → open the CoE Core solution → select “Versions” → click “Refresh”.
This forces Dataverse to re-check the installed version.
In Power Automate, open the CoE solution and check if any flows are in a failed or suspended state. If you see any, please turn them off and back on.
Large flows, sync jobs, or heavy activity can trigger “TooManyRequests.” If possible, pause those while retrying the update.
This helps the notification system pick up the correct version.
Expected Behavior
I expect the update(s) to complete successfully.
What solution are you experiencing the issue with?
Core
What solution version are you using?
4.43
What app or flow are you having the issue with?
Power Platform CoE
What method are you using to get inventory and telemetry?
None
Steps To Reproduce
Download and Extract Latest CoE Version
Download the latest .zip from [aka.ms/CoeStarterKitDownload].
Extract the package before proceeding. [learn.microsoft.com]
Clean Unmanaged Layers
These unmanaged changes block updates.
In your CoE environment, open the CoE Admin Command Center app.
Navigate to CoE flows, identify any flows with unmanaged layers (layer icon).
Use “See solution layers” and then Remove unmanaged layer. [learn.microsoft.com]
Import the New Solution
In the target environment:
Import the solution using Upgrade (default).
Anything else?
No response</issue_description>
<agent_instructions>Analyze why the CoE Core upgrade from version 4.43 to 4.50.x fails with the error ‘CanvasApp import: TooManyRequests’. Provide the root cause, confirm whether this is a kno...
✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.