Power Automate · Cloud flows: connector and api errors
ActionFailed
Short answer
ActionFailed in a Power Automate cloud flow: An action returned a failure status. This is a generic wrapper. The actual error details are in the action's output body. The most likely fix is to check action outputs for API error.
VerifiedLast verified
01Error text
ActionFailed02Likely causes
- The downstream API returned a 4xx or 5xx error
- A child flow (called via "Run a Child Flow") failed
- A custom connector returned an unexpected response format
- The action's configure-run-after settings caused it to execute after a prior failure
03How to fix it
- Open the failed run and select the failed action.
- Expand Outputs to display the actual error message and status code from the API.
- Fix the underlying issue based on the specific API error (review the 400, 401, 403, and 404 entries in this reference).
- If the action should run even when prior actions fail, check its Configure run after settings.
04Official documentation
→Related errors
- BadRequest (400)BadRequest (400) in a Power Automate cloud flow: The connector API rejected the request because the input data is malformed or invalid. The most likely fix is to validate input data format.
- NotFound (404)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.
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