pnp / pnp/pnpframework

Error: "The request uses too many resources." when executing "Invoke-PnPSiteTemplate"

Open
#672 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
C#
Stars
259
Forks
161
Avg merge
10h 33m
Merged PRs (30d)
1

Description

I use PnP PowerShell to provision my portals in SharePoint Online.

One such portal is deployed with Github Actions (CI/CD) across different site collections (same Tenant). This portal has subsites that are also provisioned with PnP PowerShell, which have been deployed without problems in DEV (3 subsites) and CERT (5 subsites), but in PRE (20 subsites) it ran without problems the first time but when I want to do an update I get the following error 'The request uses too many resources.' when trying to run the command "Invoke-PnPSiteTemplate"

Script that runs at the site collection level:
Invoke-PnPSiteTemplate -Path Templates/Provisioning_Level01.xml -ErrorAction Stop

Error in PRE:
image

Provisioning_Level01.xml:
Provisioning_Level01.zip

However, if the following XML is provisioned there is no error (in all environments).
Provisioning_Branding.zip

This same XML (Provisioning_Level01.xml) is provisioned in DEV and CERT without problem, we only found two differences between these environments:

  • PRE has 20 subsites (subsite provisioning scripts run without errors in all environments, the script running at the site collection level is the one giving the error in PRE).
  • PRE was created two weeks ago, unlike DEV and CERT which were created at the beginning of the year (I don't know if there is something different in the new site collections).

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing the Invoke-PnPSiteTemplate command and the attached Provisioning_Level01.xml, then compare it with Provisioning_Branding.zip, which does not trigger the error. Reproduce the update in the PRE environment and investigate why the larger subsite configuration exceeds the request resource limit; done means the Level01 provisioning update completes or the limiting condition is clearly documented.

Written by the indexing model from the issue text.

Assessment

Tech stack
csharp, powershell
Domain
devops, tooling
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.