Power Automate 404 and 500 errors — how to read and fix them
A 404 in Power Automate means the record, file, or item an action referenced doesn’t exist or its path/ID is wrong — often a deleted record, the wrong environment, or a blank dynamic ID. A 500 means the service accepted the request but failed processing it, usually a malformed body or unexpected null. Immediate fix: open the run history, check the failing action’s actual inputs, and confirm the record and environment are correct; for a 500, read the raw outputs for the underlying message. Durable fix: guard against blank IDs before the action, validate the request body and required properties, and add a retry policy for transient 500s.
404 Not Found
The record, list, file or item the action referenced does not exist or the path/ID is wrong. Common with a deleted record, a wrong environment, or a dynamic ID that resolved to blank.
- 1Open the run history and read the failing action's inputs — check the ID/path it actually used.
- 2Confirm the record still exists and you are pointing at the right environment / site.
- 3Guard against blank IDs before the action (a blank dynamic value often produces a 404).
500 Internal Server Error
The service accepted the request but failed while processing it — often a malformed body, an unexpected null, or a transient service issue.
- 1Read the raw outputs of the failing action for the underlying message.
- 2Validate the request body (especially JSON) and that every required property is present and correctly typed.
- 3Add a retry policy for transient 500s, and re-test with "View raw inputs" to reproduce.