Erreur 404

(0) Share

Report

Posted on by SC-28041802-0

J'ai trouvé cette erreur lors de l'exécution du flux de réccurent :"rror from microservice: {"status":404,"message":"Item not found","source":"api.connectorp.svc.ms"}
clientRequestId: 42f3fd58-0344-4c43-9053-3b7690f643a7
serviceRequestId: 67760ea2-90cd-c000-e3f6-05065bc3f404"

comment la corriger

Categories:

Using flows

Building flows

I have the same question (0)

All responses (3)

Answers (0)

Sort by

David_MA 14,424 Super User 2026 Season 1 on at

Like (0)

Report
Copy link

Link copied!

Please share a screen shot of the action that contains the error from the flow run. Otherwise, about the only thing I can tell you is that the error is telling you that it is looking for something that no longer exists and was probably deleted or the permissions were changed on the item and you no longer have access.

We need information such as this which provides specific rather than generic information:

In this flow, an HTTP request was updating a list item in SharePoint. The action failed because the list item was deleted just like the error message indicates.

Was this reply helpful? Yes No
Sunil Kumar Pashikanti 2,069 Moderator on at

Like (0)

Report
Copy link

Link copied!
Hi @SC-28041802-0,

A 404 “Item not found” error in a recurring flow almost always means the flow is trying to read or update an item that doesn’t exist at runtime (anymore). Usually, this happens because an ID or file path is empty/outdated, or a previous search step didn't actually return a result, but the flow tried to use the ID anyway.

A few quick things to check in your Run History:

Find the first failed action (Get item, Update file, etc.) and look at the ID or Identifier being passed in. Is it actually there, or is it blank?

If that ID is coming from a previous step, check if that step actually found anything.

The Fix: Add a simple condition/guard before that failing step. Only run the "Get" or "Update" action if the result from your search step isn't empty.

Most of the time, this is just a case of needing to fetch a fresh, valid ID in the same run or telling the flow to skip the action if nothing was found.

As suggested by @David_MA, If you can share which connector and action are failing, we can help you with identifying the isseu and the specific logic to fix it!

Was this reply helpful? Yes No
Suggested answer

11manish 2,126 on at

Like (0)

Report
Copy link

Link copied!

The “404 – Item not found” error in Power Automate typically occurs when a flow references a resource (file, record, script, or list item) that no longer exists or is

not accessible under the current connection.

The most reliable fix is to identify the failing action, reselect the resource in that step to refresh its reference, and ensure the connection has proper access.

Avoid hardcoded IDs and instead dynamically retrieve resources to prevent this issue in recurring flows.

Was this reply helpful? Yes No