A group of Microsoft Products and technologies used for sharing and managing content, knowledge, and applications.
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.