My SharePoint site has reached metadata limit.

Sarita Patare (Admin) 0 Reputation points
2026-08-28T14:58:05.4733333+00:00

My SharePoint site has Reached metadata limit. There is list on my SharePoint site which has power automate workflow associated with it.due to error in workflow it ran in loops and caused metadata size increase.

I am getting warning on my SharePoint site.

This site is close to the metadata limit. Create more space by deleting old file versions and duplicate files in lists, libraries.

Microsoft 365 and Office | SharePoint | Other | Other
0 comments

2 answers

Sort by: Oldest
Most helpful Newest Oldest

  1. AI answer

    2026-08-28T14:58:20.0666667+00:00

    The warning means the site is approaching or has exceeded the SharePoint Online overall site metadata limit. In SharePoint Online, metadata such as file size, author, creation date, file versions, lists, and other system-generated information counts toward that limit.

    In this scenario, the practical remediation is to create more metadata space by cleaning up content that generates excess metadata:

    1. Delete old file versions in the affected lists and libraries.
      Multiple versions of the same file or list item increase metadata usage.
    2. Delete duplicate files in the affected lists and libraries.
      Copies of the same file also contribute to metadata growth.
    3. Since the issue started after a workflow loop, check whether the workflow created excessive versions or duplicate items, and remove that excess content first.
    4. If SharePoint 2013 workflows on the site were suspended because limits were exceeded, remove the workflows that exceeded their limits from: Settings > Site Settings > Workflow Settings > Workflow Health
    5. On the Workflow Health page, the workflows that caused suspension can be identified by running ShowScopeDebugInfo() in the browser developer console. If StatusDetails shows MaxTopicSize and MaxCorrelationFilter, it indicates the site suspended all SharePoint 2013 workflows.
    6. After removing the problematic workflows, allow time for cleanup. The process is not instant. The Workflow Health status changes to Connected when cleanup is complete.

    SharePoint Online documentation also states the overall site metadata limit is 1000 GB per site.

    References:

    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

  2. Aetherin 1,465 Reputation points Independent Advisor
    2026-08-28T15:14:52.8366667+00:00

    Hi @Sarita Patare (Admin),

    The AI response correctly explains that this warning appears when the site is approaching or has exceeded its overall metadata limit. You can follow its recommendation to remove unnecessary file versions, duplicate files, and excess content generated by the looping flow. Microsoft specifically recommends deleting old file versions and duplicate files from the affected lists and libraries.
    However, the Workflow Health, ShowScopeDebugInfo(), MaxTopicSize, and MaxCorrelationFilter instructions apply specifically to legacy SharePoint 2013 workflows, not Power Automate flows. Therefore, that section does not apply to the Power Automate flow described in this case.

    For the affected Power Automate flow, I recommend:

    • Turn off or correct the flow first to prevent further metadata growth.
    • Review its run history to determine when the loop started and what content it affected.
    • Remove unnecessary list items, duplicate files, and excessive file versions created during that period.
    • Review the version history settings for the affected document libraries to help prevent the issue from recurring.

    If excessive file versions are a major contributor, a SharePoint or Global Administrator can generate a version storage report and consider running a version-trimming job for the affected library or site. Microsoft recommends running a What-If analysis first because versions removed by a trimming job are permanently deleted and bypass the Recycle Bin.

    Also check whether the affected content is governed by a retention policy or eDiscovery hold, as protected content and versions remain subject to the applicable retention or hold requirements.

    For clarification, Microsoft documents an overall site metadata limit of 1,000 GB per site. This is separate from the regular 25 TB maximum storage limit per site collection, so the two limits should not be confused.

    After completing the cleanup, allow some time for SharePoint to process the changes. Version-trimming jobs run asynchronously and, depending on the size of the site or library, may take a few days to complete. If the warning remains after the cleanup has finished, open a Microsoft 365 support request so Microsoft can investigate the site-specific metadata consumption.

    I hope this experience may help serve as a useful reference for your scenario.

    If the answer is helpful, please kindly click "Yes" button below. If you have extra questions about this answer, please click "Comment".    

    Note: Please follow the steps in the forum documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

    Was this answer helpful?

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.