Power Automate · Cloud flows: connector and api errors
NotFound (404)
Short answer
NotFound (404) in a Power Automate cloud flow: The resource the action is trying to access doesn't exist. The most likely fix is to verify resource exists, update references.
VerifiedLast verified
01Error text
NotFound
40402Likely causes
- A SharePoint list, library, or site was renamed or deleted
- An Outlook folder or Teams channel was removed
- The flow references a hardcoded ID for a resource that no longer exists
- The Dataverse table or row was deleted by another process
03How to fix it
- Check that the resource still exists in the target service.
- If it was renamed, update the action to use the new name or ID.
- Replace hardcoded IDs with dynamic lookups where possible (for example, "Get items" with a filter instead of "Get item" with a static ID).
- Add error handling: configure the next action to Run after > has failed and handle the 404 gracefully.
04Official documentation
→Related errors
Test every fix in a non-production environment before you apply it to production. See how entries are verified.
More for Power Automate work:Open Power Automate jobs