Others

How to Fix 404 Item Not Found Error When Creating Tables in Power Automate

Kushani Nimanthika Sep 28, 2026 869 views

Question details

The user needs to resolve a '404 Item not found' error that occurs in a Power Automate flow designed to create a table and update a row following a Microsoft Forms submission.

Product: Microsoft Power Automate
Device & OS: not provided
Scenario: Automating data entry by triggering a flow from a Microsoft Forms submission to create a table and update a row in Excel.
Observed behavior: The Power Automate flow fails to execute successfully, returning a '404 Item not found' error during the table creation or row update action.

Before you start

Verify that the target Excel file, folder, and SharePoint site referenced in your Power Automate flow still exist and that your account has the correct read and write permissions to access them.

Solution 1Recommended

Seek Assistance in the Microsoft Power Automate Community

Because this involves complex flow configurations, posting your specific setup in the dedicated community allows specialized engineers to pinpoint the missing item reference.

Power Automate 404 errors are often highly specific to your environment's dynamic content, tenant permissions, or flow structure. The official Microsoft Power Automate Community is equipped to handle detailed log analysis.

Gather flow details

Take detailed screenshots of your Microsoft Forms trigger, the table creation action, row identifiers, and the overall flow configuration.

Visit the community forum

Navigate to the official Microsoft Power Automate Community website and sign in with your Microsoft account.

Post your issue

Create a new topic detailing your 404 Item Not Found error. Attach your screenshots and describe the dynamic content variables you are using so engineers can assist you effectively.

Seek Assistance in the Microsoft Power Automate Community

Protect your data: Always blur or redact any sensitive personal, financial, or organizational information from your screenshots before posting them in public forums.

Solution 2

Manually Verify File Paths and Dynamic Content

Check your flow's action settings to ensure all file paths, site addresses, and table IDs are accurate and accessible.

Free Microsoft Office alternative

Boost Your Productivity with WPS Office

While resolving complex automation flows in Microsoft ecosystems, consider switching to WPS Office for your daily document, spreadsheet, and presentation tasks. It offers a lightweight, highly compatible, and user-friendly experience without the heavy subscription costs.

1. Download WPS Office: Visit the official WPS Office website and download the free installation package for your operating system.
2. Install the software: Run the installer and follow the on-screen instructions to set up WPS Office on your computer.
3. Open your spreadsheets: Launch WPS Spreadsheets to seamlessly open, edit, and manage your Excel files with full format compatibility.

Fully compatible with Microsoft Excel (.xlsx), Word (.docx), and PowerPoint (.pptx) formatsLightweight installation with blazing-fast launch timesFamiliar user interface requiring zero learning curve for Office usersBuilt-in advanced PDF editing and conversion tools

microsoft office alternative - wps office

Frequently Asked Questions

Why do I get a 404 error when updating an Excel row in Power Automate?

This error typically occurs if the file has been moved, renamed, or deleted, or if the flow is using an incorrect dynamic File ID. It can also happen if the user connection authenticating the flow lacks permission to access the SharePoint site or OneDrive folder.

How do I find the correct Table ID in Power Automate?

You can manually select the table from the dropdown menu within the Excel action. If the table is generated dynamically, you should use the 'Get tables' action first, and then map the Table ID from its output to your update row action.

Can I test my flow to see exactly where the 404 error happens?

Yes, you can click the 'Test' button in the upper right corner of the flow editor. Running a manual test or using data from a previous failed run allows you to inspect the inputs and outputs of each step, helping you identify exactly which action is throwing the item not found error.

Office Quick Solutions