logo
search
SharePoint Document Issues

How to Remove Duplicate SharePoint List Items from a Broken Flow

Maira MehtabMaira Mehtab Sep 28, 2026 869 views

Question details

A runaway Power Automate flow has created duplicate SharePoint list items, caused throttling, and continues to produce recycle-bin activity even after being deleted, resulting in inconsistent list views for different users.

Product
Microsoft SharePoint and Power Automate
Device & OS
not provided
Scenario
Attempting to clean up duplicate list items and resolve backend synchronization issues after a Power Automate loop malfunction.
Observed behavior
Duplicate items continue to appear, throttling is triggered, recycle-bin activity continues post-deletion, and users see inconsistent data across different SharePoint list views.
Before you start

Verify in your Power Automate portal that the problematic flow has been completely turned off or deleted to prevent it from generating further duplicates while you attempt to clean up the list.

Solution 1Recommended

Manually Verify Sync Status and Delete Duplicates

Check the SharePoint list across multiple views and browsers to confirm current sync status, then manually delete the duplicates if you have the appropriate permissions.

Often, backend delays or browser caching can make it appear as though deleted items are returning. Verifying the list across different environments helps isolate whether the issue is local or server-side.

1
Check different browsers and list views

Open your SharePoint list in an incognito window or a completely different browser to rule out local caching issues. Switch between different list views using the view dropdown menu at the top right to see if the duplicates appear consistently across all views.

2
Manually delete duplicate items

Ensure you are logged in as a user with at least Edit permissions. Select the duplicate list items by checking the circles next to their titles, then click the 'Delete' button in the top command bar.

3
Monitor the site Recycle Bin

Navigate to the site's Recycle Bin via the Site Contents menu to check if automated deletion activity is still occurring. Ongoing automated activity indicates the flow's processes are still queued on the backend.

Permission Requirement: You must have at least Edit or Full Control permissions on the specific SharePoint list to successfully delete items.
Free Microsoft Office alternative

Simplify Document Management with WPS Office

While resolving complex SharePoint and Power Automate backend sync issues requires dedicated Microsoft support, you can simplify your daily document editing by switching to WPS Office. It provides a lightweight, comprehensive suite for all your essential office tasks without the heavy overhead of complex cloud automations.

  1. 1. Download the software: Visit the official WPS Office website and download the free installation package for your operating system.
  2. 2. Install and launch: Run the installer and follow the quick setup prompts. Launch WPS Office directly from your desktop.
  3. 3. Open your files: Seamlessly open, edit, and save your existing Word, Excel, and PowerPoint files locally without worrying about backend cloud sync errors.
Fully compatible with Microsoft Office formats (.docx, .xlsx, .pptx).Lightweight architecture ensures fast installation and smooth performance.Familiar tabbed user interface requires zero learning curve.Robust offline capabilities allow you to work without depending on cloud synchronization.
microsoft office alternative - wps office

Frequently Asked Questions

Why does my deleted Power Automate flow still affect my SharePoint list?

When a runaway flow creates thousands of items, it triggers SharePoint throttling and creates a massive queue of pending operations on Microsoft's backend servers. Even after you delete the flow, these queued actions may continue executing until the queue is completely empty.

How can I prevent a Power Automate flow from looping and duplicating items?

Ensure your flow's trigger conditions do not recursively trigger themselves. For example, if a flow is triggered 'When an item is modified' and the flow itself modifies the same item, it will create an infinite loop. Always use specific trigger conditions or separate lists to break the loop.

What should I do if team members see different data on the same SharePoint list?

This usually indicates a synchronization failure or aggressive caching on Microsoft's backend, often caused by throttling. First, ask users to clear their browser cache and check different list views. If the data remains out of sync across different accounts, a Microsoft 365 administrator must escalate the issue to Microsoft Support to fix the backend sync.