List rows in excel action is giving table guid when the flow runs and this action fails

(1) Share

Report

Posted on by CU27041500-0 Microsoft Employee

The error i am getting is in the action “List rows in Excel” after one flow run is completed, this error "Graph API Error" occurred for the second flow run when the excel sheet was read again by this Action.
After the flow fails i go into the power automate, I have to manually update the table name and file path again.
Please see the attachments below and help.

Error Body - {

"status": 404,

"message": "Graph API request failed. Error code is 'itemNotFound'. Error message is 'The resource could not be found.'.\r\nclientRequestId: 8800e30d-42f3-4a11-ad01-8e61bbd17a88\r\nserviceRequestId: 589629e6-0941-4fc5-80d9-9a471ba1d099",

"error": {

"message": "Graph API request failed. Error code is 'itemNotFound'. Error message is 'The resource could not be found.'."

"source": "excelonline-wus.azconn-wus-001.p.azurewebsites.net"

}

Error Header - {

"Cache-Control": "no-store, no-cache",

"Pragma": "no-cache",

"Strict-Transport-Security": "max-age=31536000; includeSubDomains",

"x-ms-request-id": "589629e6-0941-4fc5-80d9-9a471ba1d099",

"X-Content-Type-Options": "nosniff",

"X-Frame-Options": "DENY",

"x-ms-environment-id": "ec2cdf53-4c3d-433a-b244-c654e47e853d",

"x-ms-tenant-id": "72f988bf-86f1-41af-91ab-2d7cd011db47",

"x-ms-subscription-id": "ec2cdf53-4c3d-433a-b244-c654e47e853d",

"x-ms-dlp-re": "GetItems|False",

"x-ms-dlp-gu": "-|-",

"x-ms-dlp-ef": "-|-/-|-|-|-",

"x-ms-mip-sl": "-|-|-|-",

"x-ms-au-creator-id": "9b93ffd6-2c96-4a0c-b67a-a0ab3b1eca76",

"Timing-Allow-Origin": "*",

"x-ms-apihub-cached-response": "true",

"x-ms-apihub-obo": "false",

"Date": "Mon, 06 Apr 2026 08:49:24 GMT",

"Content-Length": "476",

"Content-Type": "application/json",

"Expires": "-1"

}

Screenshot 2026-0...

Your file is currently under scan for potential threats. Please wait while we review it for any viruses or malicious content.

Categories:

Building flows

Using connectors

I have the same question (0)

All responses (3)

Answers (0)

Sort by

David_MA 14,761 Super User 2026 Season 1 on at

Like (1)

Report
Copy link

Link copied!

Your attachments are still under review but based on the error message the issue is not necessarily with your workflow. The error message says it cannot find the spreadsheet, which would indicate someone deleted the file. That is certainly possible and one of the hazards of using this action. Did you check to make sure the file is still in the location you pointed it to in your workflow?

Was this reply helpful? Yes No
Suggested answer

11manish 2,647 on at

Like (1)

Report
Copy link

Link copied!

The "Graph API Error – itemNotFound (404)" occurs because the Excel connector is referencing a file or table that no longer matches its cached internal ID.

This typically happens when the Excel file or table is recreated, renamed, or dynamically referenced.

The most reliable fix is to use a static Excel file with a fixed table name, avoid recreating the file, and reference it using the file Identifier (via “Get file metadata”) instead of a path.

This ensures the connector always points to the correct resource across runs.

Was this reply helpful? Yes No
Suggested answer

Valantis 6,031 on at

Like (1)

Report
Copy link

Link copied!

Hi @CU27041500-0,

Good points from the others. One thing worth adding that your error headers reveal: the response has `x-ms-apihub-cached-response: true`. This means Power Automate returned a cached response from a previous run rather than making a fresh API call. The cached response contained an internal table GUID that is no longer valid, which is exactly why the 404 fires on the second run but not the first.

This cached response behavior is a known issue with the Excel Online connector when the file path or table reference changes between runs or when the file is modified in a way that invalidates SharePoint/OneDrive's internal item ID.

Beyond 11manish's fix of using Get file metadata for the identifier, two additional things to check:
First, check if your flow or another process is recreating or copying the Excel file between runs. Every time SharePoint creates a new file even with the same name, it gets a new internal item ID. The connector caches the old one and fails on the next run.

Second, make sure the Excel file is not open by a user when the flow runs. Excel Online locks the file and Graph API can return stale or cached metadata in that state.
The permanent fix for the GUID issue specifically: open the List rows action, delete the Table field value completely, save and reopen the action, then re-select the table from the dropdown. This forces the connector to re-resolve the table name to a fresh ID rather than storing the GUID directly.

Best regards,

Valantis

✅ If this helped solve your issue, please Accept as Solution so others can find it quickly.

❤️ If it didn’t fully solve it but was still useful, please click “Yes” on “Was this reply helpful?” or leave a Like :).

🏷️ For follow-ups @Valantis.

📝 https://valantisond365.com/

💼 LinkedIn

▶️ YouTube

Was this reply helpful? Yes No