Troubleshoot SharePoint Flow HTTP 500 and 502 Errors
Question details
The user needs to investigate intermittent HTTP 500 and 502 errors in a SharePoint flow after adding fields.
- Product
- Microsoft SharePoint and Power Automate
- Device & OS
- not provided
- Scenario
- A flow creates SharePoint list items after new fields are added to a form, list, and flow.
- Observed behavior
- The Create item action intermittently fails with an HTTP 500 or 502 error.
Identify a failed flow run and the SharePoint list it targets. Note which fields were recently added and whether the same inputs also fail in other runs.
Check the Create item fields and connection
Use the failed run details to check whether the new fields, expressions, or SharePoint connection need attention.
In Power Automate, open My flows, select the flow, and open a failed run under Run history. Expand Create item and review its inputs, outputs, status code, and error message.
Open the target SharePoint list and select Settings > List settings. Check the new columns, their types, and any required fields against the values supplied in Create item.
Open the flow in Edit mode and expand Create item. Check the site address, list name, dynamic content, and expressions for each new field; make sure the values match the corresponding column types.
In Power Automate, open Connections and check the SharePoint connection used by the flow. Reconnect if needed, then save and test the flow with a sample submission.
Share the flow details with Microsoft support
Use this option if the errors continue or the run history does not explain the intermittent failures.
Organize SharePoint List Data with WPS Office
WPS Office is a free, lightweight alternative for working with documents and spreadsheets in a familiar interface. Its Office format support makes it easier to move existing files into WPS, although it cannot fix SharePoint or Power Automate service errors.

Frequently Asked Questions
Where can I find the error details for a failed flow?
In Power Automate, open My flows, select the flow, and choose the failed run under Run history. Expand Create item to inspect the inputs, outputs, and error message.
Could a new SharePoint column cause the Create item action to fail?
A new field can cause problems if its mapping, value type, expression, or required status does not match the SharePoint column. Compare the Create item inputs with the columns in SharePoint List settings.
Should I rerun a flow after an HTTP 500 or 502 error?
First check the target SharePoint list for an item from the failed run. If an item was created despite the reported error, rerunning the flow could create a duplicate.
What should I include in a Power Automate Community post?
Include the error code and message, screenshots of the failed Create item action, relevant field mappings and expressions, and a description of when the failures occur. Remove sensitive information before posting.




