logo
search
SharePoint Document Issues

Fix Power Automate Update Item Cannot Find List Item Error

Aamir Naveed AkramAamir Naveed Akram Sep 27, 2026 869 views

Question details

The user needs to resolve an issue where an automated workflow fails because it is unable to locate a specific list item to update.

Fix Power Automate Update Item Cannot Find List Item Error
Product
Power Automate / SharePoint
Device & OS
not provided
Scenario
Running an automated vacation-request flow that collects form responses, adds them to a SharePoint list, requests approvals, and creates events.
Observed behavior
The flow initially worked but now consistently fails at the 'Update item' action, returning an error stating the SharePoint list item cannot be found.
Before you start

Before troubleshooting, open your Power Automate run history for the failed flow to identify the exact step where the error occurred and ensure you still have proper edit permissions for the target SharePoint list.

Solution 1Recommended

Verify and Map the Correct SharePoint Item ID

The most common cause of this error is mapping a Form Response ID or another unrelated field instead of the actual SharePoint List Item ID.

When an item is created in SharePoint, it is assigned a unique identifier (ID). If your 'Update item' action uses an ID from a different connector (like Microsoft Forms), SharePoint will not be able to find the item.

1
Open flow in Edit mode

Navigate to the Power Automate dashboard, select 'My flows', and click the 'Edit' button on your failing vacation-request flow.

2
Expand the Update item action

Scroll down the flow workflow and click on the 'Update item' action card to expand its settings.

3
Clear the incorrect ID

Check the 'Id' field. If it is populated with 'Response Id' or an ID from a different step, delete it.

4
Select the correct dynamic content

Click inside the 'Id' field to open the dynamic content menu. Scroll to the section labeled 'Create item' (the SharePoint action) and select 'ID'. Save and test your flow.

Verify and Map the Correct SharePoint Item ID
Dynamic Content Verification: Always ensure the SharePoint icon is visible next to the 'ID' token in the dynamic content menu, confirming it belongs to the SharePoint connector.
Free Microsoft Office alternative

Looking for a Lightweight Document Solution? Try WPS Office

While Power Automate and SharePoint handle complex automated data workflows, everyday document creation should remain simple. WPS Office offers a free, lightweight, and highly compatible alternative to Microsoft Office, perfect for your daily document management needs.

  1. 1. Download the installer: Visit the official WPS Office website and click the free download button for your operating system.
  2. 2. Install the software: Run the downloaded installation file and follow the quick on-screen instructions.
  3. 3. Open and edit seamlessly: Launch WPS Office to instantly open, edit, and save your existing Microsoft Office documents without format loss.
Highly compatible with Microsoft Word, Excel, and PowerPoint formats (.docx, .xlsx, .pptx).Lightweight installation with blazing fast startup speeds compared to traditional Office suites.All-in-one suite with a familiar, easy-to-navigate user interface.Seamless offline editing for your exported SharePoint lists and reports.
microsoft office alternative - wps office

Frequently Asked Questions

Why does my Power Automate flow randomly say the list item is not found?

This often occurs if the SharePoint list item was manually deleted by a user or modified by a conflicting flow before your current flow reaches the 'Update item' step. It can also happen due to temporary indexing delays in SharePoint.

Can I use the Form Response ID to update a SharePoint item?

No. The 'Update item' action requires the specific List Item ID generated internally by SharePoint when the item is created. You cannot use the ID from the Microsoft Forms trigger.

How do I view the run history to see exactly where my flow failed?

Go to 'My flows' in your Power Automate dashboard, click on the name of the flow (do not click Edit), and look at the '28-day run history' section at the bottom. Clicking on any failed run will open a visual breakdown of where the error occurred.