SharePoint List Trigger Misses Bulk Imported Items: What Site Owners Should Check

When you bulk import items into a SharePoint list, the Power Automate trigger you set up may not run for every item. Site owners often notice that some or all of the imported records are missing from the triggered flow. This happens because SharePoint list triggers, especially the When an item is created or modified trigger, behave differently during bulk operations. This article explains the exact cause of this behavior and shows you what settings to check so your flows process every imported item.

Why SharePoint List Triggers Skip Bulk Imported Items

The root cause lies in how SharePoint handles bulk operations. When you use the built-in Import from CSV wizard or a third-party tool to add many items at once, SharePoint often creates those items in a single batch call. Power Automate’s When an item is created or modified trigger listens for individual creation events. A batch creation can generate only one event for the entire set, which the trigger may ignore or treat as a single item update. Additionally, the trigger has a built-in debounce mechanism that waits a few seconds after the last change before firing. During a rapid import, the debounce period may expire before all items are created, causing the trigger to miss later items. This is not a bug — it is a design limitation of the trigger’s event model.

How the Trigger Event Model Works

The When an item is created or modified trigger uses SharePoint’s change log. When you add items one at a time through the SharePoint UI, each addition writes a separate entry in the change log. The trigger picks up each entry and runs the flow. But bulk imports often write a single change log entry for the entire batch. The trigger sees only one creation event and fires once. If your flow depends on processing each item individually, the remaining items are never processed.

The Role of Versioning and Approval

SharePoint versioning settings also affect trigger behavior. If your list has Require content approval enabled, items imported in bulk are created in a Draft state. A second event — approval — is required to move them to Published. The trigger can catch this second event if configured correctly. Without approval, the imported items may stay in Draft and never trigger the flow. For lists without approval, the bulk creation event is the only event, and the trigger may miss it.

Steps to Check Trigger Settings and Fix Missing Items

Follow these steps to verify your trigger configuration and adjust it to catch bulk imported items.

1. Open your Power Automate flow in edit mode
   Go to Power Automate, select My flows, and click the flow that uses the SharePoint list trigger. Click the Edit button at the top of the page.
2. Check the trigger type
   Click the trigger step labeled When an item is created or modified. Verify that the trigger is set to SharePoint and that the site address and list name are correct. If the trigger uses a different connector, such as When a file is created, it will not work for list items.
3. Add a trigger condition to filter by the Modified field
   In the trigger settings, click the ellipsis (…) and select Settings. Under Trigger Conditions, add this expression: @equals(triggerOutputs()?['body/Modified'], triggerOutputs()?['body/Created']). This condition ensures the flow runs only when the item’s Modified date equals its Created date — which is true for the first creation event. For bulk imports, the trigger may fire once with a matching Modified and Created value. This condition helps capture that single event.
4. Enable content approval on the SharePoint list
   Go to the SharePoint list, click the gear icon, and select List settings. Under Versioning settings, set Require content approval to Yes. Set Who can view items to Draft items if needed. After you import items in bulk, each item will be in Draft. You or a flow can then approve them, triggering a second event that the flow can catch.
5. Test the flow with a single manual creation
   Add one item manually through the SharePoint list interface. Confirm that the flow runs for that item. If it does, the trigger is working. The issue is specific to bulk imports. If the flow does not run for a single item, check the trigger connection and permissions.
6. Perform a bulk import using Quick Edit
   Open the SharePoint list, click Quick Edit (the grid view), and paste your data from Excel. This method creates items one at a time, generating individual change log entries. The trigger should catch each item. After pasting, click Done to save.

If the Trigger Still Misses Items After the Main Fix

Even after applying the steps above, you may encounter situations where bulk imported items are still missed. Here are the most common scenarios and their solutions.

“My flow runs only once for the entire import”

This confirms the batch event issue. The trigger fires once, and the flow processes only the first item in the batch. To fix this, restructure your flow to use a Apply to each loop that reads from a separate data source, such as a CSV file stored in SharePoint or a temporary list. Alternatively, use the When a file is created or modified trigger for a CSV file, then parse the file and create list items inside the flow. This bypasses the list trigger entirely.

“Items appear in the list but the flow never runs”

Check the Power Automate run history. Go to My flows, select the flow, and click Run history. Look for any failed runs. If there are no runs at all, the trigger did not fire. This confirms the batch event was missed. Apply the trigger condition from Step 3 and reimport the items. If the issue persists, switch to Quick Edit for the import.

“The flow runs, but some items are skipped”

This can happen when the trigger fires for the first few items but the debounce period expires before all items are created. The solution is to increase the trigger’s Polling interval in the trigger settings. Set it to 5 or 10 minutes. This gives SharePoint time to complete the batch and write a single change log entry. Keep in mind that a longer interval means slower processing for new items.

Power Automate Trigger vs. SharePoint Event Receiver: Key Differences

Item	Power Automate Trigger	SharePoint Event Receiver
How it listens	Polls the change log periodically	Runs synchronously on the server when an item changes
Bulk import handling	May miss batch events due to debounce	Runs for each item in the batch
Configuration effort	No-code setup in Power Automate	Requires custom code (C# or PowerShell)
Trigger condition flexibility	Limited to expressions on trigger outputs	Full control via event receiver code

SharePoint event receivers are more reliable for bulk imports, but they require developer skills and server-side deployment. For most site owners, adjusting the Power Automate trigger settings and using Quick Edit for imports is the practical fix.

Now you know why the SharePoint list trigger misses bulk imported items and what settings to adjust. Start by enabling content approval and adding the Modified equals Created condition to your trigger. For future imports, use Quick Edit instead of the CSV wizard to generate individual creation events. If you need absolute reliability for large imports, consider building a flow that reads from a CSV file and creates items one at a time inside the flow logic.