Server error? Not possible to save items into sharepoint list

(2) Share

Report

Posted on by WorkingRicardo

878

My issue is not solved, this was marked as solved before me coming back from holiday Solved: Server error? Not possible to save items into sharepoint list

I repost my initial question in the hopes to get some help:
UPDATE: This just happened with another sharepoint list integrated form app that only has 200 items. So don't think item size was a problem (this app was working fine well after the 5000 mark which we reached around a year ago).

Have this sharepoint list form edited in Power Apps running for 2 years now. It has around 14k items. All of the sudden today the PowerApps button that had a SubmitForm(SharepointForm) in its Onselect is giving a bunch of errors

I also go to the PowerApps editor and get some server error. Tried deleting the sharepoint connection and re-establishing it. Nope. What can i doooooo

(The request was not sent due to repeated server errors.

@ Network error when using the Patch function: The request has not been sent, or the server has not responded. Check your Internet connection.
@ Could not save. The request has not been sent, or the server has not responded. Check your Internet connection. Server response: Orders error: null
@ SP detail: The request has not been sent, or the server has not responded. Check your Internet connection.

Categories:

Building Power Apps

I have the same question (0)

All responses (6)

Answers (0)

Sort by

WorkingRicardo 878 on at

Like (1)

Report
Copy link

Link copied!

Update: an user of the app told me he could save and edit, he just let the app charge for a looooooooooooooooong time and then he could do save and edit.

Was this reply helpful? Yes No
Suggested answer

Valantis 6,163 on at

Like (1)

Report
Copy link

Link copied!

Hi @WorkingRicardo,

The fact that it works after waiting a long time confirms this is not a code or configuration issue, it's a backend latency problem between Power Apps and SharePoint.

Check admin.microsoft.com > Health > Service health for any active Power Apps or SharePoint incidents. There have been recent reports of SharePoint connector slowness specifically in Europe.

If service health shows nothing, check:

- Whether the slowness affects all users or specific ones
- Whether it's happening at consistent times of day (could indicate scheduled jobs on your SharePoint tenant causing load)
- Open browser DevTools Network tab while saving and check which request is slow and what status code it returns

The 14k item list with indexed columns is unlikely the cause since it worked fine before and a 200-item list now has the same issue. This points to something external to your app.

Best regards,

Valantis

✅ If this helped solve your issue, please Accept as Solution so others can find it quickly.

❤️ If it didn’t fully solve it but was still useful, please click “Yes” on “Was this reply helpful?” or leave a Like :).

🏷️ For follow-ups @Valantis.

📝 https://valantisond365.com/

💼 LinkedIn

▶️ YouTube

Was this reply helpful? Yes No
Suggested answer

11manish 2,724 on at

Like (0)

Report
Copy link

Link copied!
Based on the symptoms you've described, this does not appear to be a SharePoint list size issue, especially since:

The problem started suddenly after the app had been working for years.

A second SharePoint-integrated Power App with only ~200 items is now experiencing the same behavior.

The errors occur during both SubmitForm() and Patch() operations.

The error messages are generic ("Server response: null", "request has not been sent", "repeated server errors").

These indicators point more toward a SharePoint-Power Apps connectivity issue, schema change, permission problem, or platform/service issue rather than the

5,000-item threshold or the 14,000-item list size.

The quickest way to isolate the issue is to:

Verify that the SharePoint list can be edited directly.

Create a brand-new test app against the same list.

Check browser network traces for the actual API error.

If a newly created app also cannot save while direct SharePoint editing works, the evidence strongly points to a Power Apps ↔ SharePoint integration issue, and opening a Microsoft Support ticket would be justified.

Was this reply helpful? Yes No
WarrenBelz 155,565 Most Valuable Professional on at

Like (0)

Report
Copy link

Link copied!

@WorkingRicardo,

Adding an answer to the question on your previous thread on this, if you select the standard SharePoint Form, but do not select to delete the Power App, it will still be there if you want to switch back. If you are really worried abot the form, refer to this blog of mine - you can copy the entire screen Code, save it to Notepad and put it back whenever you need to.

Was this reply helpful? Yes No
WorkingRicardo 878 on at

Like (1)

Report
Copy link

Link copied!

Hey @11manish @WarrenBelz Ty for your replies. Yes i tried creating another simpler powerapps canvas app that edits the sharepoint list and that is possible, no error. So apparently must be something on my sharepoint integrated app. What tests I can run to further isolate this or give you more information?

Was this reply helpful? Yes No
WarrenBelz 155,565 Most Valuable Professional on at

Like (0)

Report
Copy link

Link copied!
Hi @WorkingRicardo,

Firstly check the OnSave code - it should be something like
SubmitForm(SharePointForm1); RequestHide()

Also the form displaying the record correctly ?

Apart from this, you could consider going a bit "scorched earth" as there is clearly something wrong with the app. If you look at this blog of mine (make sure you have both the Screen and OnStart code copied to Notepad) , restore the standard SP app and delete the Power App, then put it all back.

Please ✅ Does this answer your question if my post helped you solve your issue. This will help others find it more readily. It also closes the item. If the content was useful in other ways, please consider answering Yes to Was this reply helpful? or give it a Like ♥
Visit my blog Practical Power Apps LinkedIn

Was this reply helpful? Yes No