Power Automate · Cloud flows: connector and api errors
BadRequest (400)
Short answer
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.
VerifiedLast verified
01Error text
BadRequest
40002Likely causes
- Sending a field with the wrong data type (string instead of number, or vice versa)
- Required fields missing from the request body
- Invalid characters in file names or list item titles
- Exceeding a field length limit (for example, SharePoint single-line text = 255 chars)
03How to fix it
- Open the failed action in run history and look at the Inputs section to display exactly what was sent.
- Compare the inputs to the API's expected schema (check the connector documentation).
- Sanitize user input with
replace()to strip invalid characters before passing to the action. - Use
substring()ortake()to truncate long values to the field's max length.
04Official documentation
→Related errors
- ActionFailedActionFailed 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.
- ContentConversionFailedContentConversionFailed in a Power Automate cloud flow: The flow couldn't convert data from one type to another between actions. The most likely fix is to use explicit type conversions.
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