You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
List items open to a blank page (SPListForm.aspx fails) on lists with an SPFx form customizer #11056
What SharePoint development model, framework, SDK or API is this about?
💥 SharePoint Framework
Developer environment
None
What browser(s) / client(s) have you tested
💥 Internet Explorer
💥 Microsoft Edge
💥 Google Chrome
💥 FireFox
💥 Safari
mobile (iOS/iPadOS)
mobile (Android)
not applicable
other (enter in the "Additional environment details" area below)
Additional environment details
SPFx 1.23.0.
Describe the bug / error
On some of our tenants, clicking an item in a list opens a blank page instead of the form. It happens on every item in the affected lists.
These lists use an SPFx form customizer from our product. The failure happens inside SharePoint itself, before our code is ever loaded. SharePoint returns the page with the correct title, but the page body is empty and the tab title changes to “Error”. The browser never makes a request for our form customizer’s files.
We can reproduce this on our own tenant. Several of our customers see the same thing on their tenants, so it doesn’t seem to be specific to one tenant.
Steps to reproduce
Open a list whose content type has an SPFx form customizer registered (DisplayFormClientSideComponentId etc.).
Click any item.
The browser goes to https://contoso.sharepoint.com/sites//_layouts/15/SPListForm.aspx?PageType=4&List=&ID= and shows a blank page with the tab title “Error”.
Expected behavior
When opening sharepoint list items, they load the SPFx form customizer
Thank you for reporting this issue. Here is an AI-generated initial response:
Classification: Bug — a blank display form is inconsistent with the documented SPFx form-customizer behavior, though the cause is unconfirmed.
You report that SPListForm.aspx shows “Error” before requesting any customizer files. That points toward form loading rather than your rendering code, but a response trace is needed to locate the failure.
A related report describes Edit/View forms failing before customizer code loads on Turkish-language sites; it does not establish the same cause here.
Upgrade check: The SPFx 1.23.2 release notes list no fix for this symptom. An upgrade from 1.23.0 is not a verified remedy.
What to do now:
Compare affected and working sites’ languages, content-type form registrations, and New/Edit/Display behavior.
Capture the failing response status, browser network trace, correlation ID, and UTC timestamp; provide them to Microsoft support.
We got the same problem.
All list form customization extensions stopped working!
Reacted by PauliusBaltrenasFlowForma, massitest3, Dmitry Kozlov, NOC-MTA105, Tim Metz, Anna Zabolotskaya, Vladimir Gubler, Nikita Kurguzov and chris4skybow
same issue in our PRD tenant. Test Tenant not affected.
Reacted by PauliusBaltrenasFlowForma, massitest3, Dmitry Kozlov, NOC-MTA105, Tim Metz, Anna Zabolotskaya, Vladimir Gubler, Nikita Kurguzov and chris4skybow
PauliusBaltrenasFlowForma commented on Oct 13, 2026
We have the same issue. The SPFx Workbench (_layouts/15/workbench.aspx) also shows a blank page.
Reacted by massitest3, kzeroa, Dmitry Kozlov, PauliusBaltrenasFlowForma, NOC-MTA105, Tim Metz, Anna Zabolotskaya, Vladimir Gubler, Nikita Kurguzov and chris4skybow
Facing similar issue where Application Customizer is used for list forms. The SPListForm.aspx is failing and request response says Unauthorized in the Network tab of Developer Tools to everyone who has access.
Reacted by Anna Zabolotskaya, Vladimir Gubler, Nikita Kurguzov and chris4skybow
PauliusBaltrenasFlowForma commented on Oct 13, 2026
10. Facing similar issue where Application Customizer is used for list forms. The SPListForm.aspx is failing and request response says Unauthorized in the Network tab of Developer Tools to everyone who has access.
This sounds like a slightly different issue, but could be related.
Reacted by Anna Zabolotskaya, Nikita Kurguzov and chris4skybow
As a potential correlation I also noticed that since this issue started to appear one of our Powershell scripts which uses PnP Powershell is failing now as the RootWeb and its ID can no longer be determined. In our test Tenant this is still working fine.
Not sure if its anyhow related but the timing + the fact that it works fine in the tenant that is unaffected by the Forms Customizer Issue as well, might show a correlation here.
Reacted by PauliusBaltrenasFlowForma, Jon Ivar Kleveland, Anna Zabolotskaya, Nikita Kurguzov and chris4skybow
Seeing the same behaviour here. As of now, only our test tenant appears to be affected.
If this update is rolled out to our production tenant, it could have a significant operational impact and would likely cause major disruption.
Update: After opening a ticket MS has confimed this Issue via SP1503038 as a recent API change
Reacted by mateusz-sintel, Jon Ivar Kleveland, PauliusBaltrenasFlowForma, michalgsintel, Anna Zabolotskaya, Vladimir Gubler, Nikita Kurguzov and chris4skybow
Same here. we have at least a dozen reports in the last hour. At what point does Microsoft reimburse for the loss of production??? 50 hours and counting
Seems that the root cause of this issue was the same as with #11059. The issue was detected by the automatic engineering systems, but due to internal complexity disabling the rollout of the new build took longer than expected. Engineering has acknowledged that their internal validation was missing key customer scenarios which is why this issue was not detected earlier. Needed updates are now in progress for the future testing and validation by the right teams.
Thank you everyone for flagging the issue openly here for others to benefit - This helped to speed up the resolution of the root cause. Highly unfortunately situation which should not happen in future, given the updates on the validation processes.
Activity
m365-agent-toolkit-assistant commentedon Oct 13, 2026
👋 Hi Rytis Daskevicius (@RytisDaskeviciusFlowForma),
Thank you for reporting this issue. Here is an AI-generated initial response:
Classification: Bug — a blank display form is inconsistent with the documented SPFx form-customizer behavior, though the cause is unconfirmed.
SPListForm.aspxshows “Error” before requesting any customizer files. That points toward form loading rather than your rendering code, but a response trace is needed to locate the failure.Upgrade check: The SPFx 1.23.2 release notes list no fix for this symptom. An upgrade from 1.23.0 is not a verified remedy.
What to do now:
Useful links:
jikleveland commentedon Oct 13, 2026
We got the same problem.
All list form customization extensions stopped working!
till-llit commentedon Oct 13, 2026
same issue in our PRD tenant. Test Tenant not affected.
PauliusBaltrenasFlowForma commentedon Oct 13, 2026
We have the same issue, someone on Reddit also:
https://www.reddit.com/r/sharepoint/comments/1x4l0k8/html_forms_created_using_the_spfx_generic_form/
BrunoMiculi commentedon Oct 13, 2026
We have the same issue. The SPFx Workbench (_layouts/15/workbench.aspx) also shows a blank page.
jusper-dk commentedon Oct 13, 2026
We've received quite a few reports from clients about this issue this morning and have been able to reproduce it in our own tenants as well.
shajumohamed commentedon Oct 13, 2026
We are using Plumsail Forms to customize SharePoint list forms and are facing this issue across multiple lists as the product depend on this feature.
NOC-MTA105 commentedon Oct 13, 2026
Facing similar issue where Application Customizer is used for list forms. The SPListForm.aspx is failing and request response says Unauthorized in the Network tab of Developer Tools to everyone who has access.
PauliusBaltrenasFlowForma commentedon Oct 13, 2026
This sounds like a slightly different issue, but could be related.
zapftho commentedon Oct 13, 2026
As a potential correlation I also noticed that since this issue started to appear one of our Powershell scripts which uses PnP Powershell is failing now as the RootWeb and its ID can no longer be determined. In our test Tenant this is still working fine.
Returns
nullin our affected Tenant.Not sure if its anyhow related but the timing + the fact that it works fine in the tenant that is unaffected by the Forms Customizer Issue as well, might show a correlation here.
brettlonsdale commentedon Oct 13, 2026
Hi - we're experiencing the same issue internally and with customers.
tomasz-sintel commentedon Oct 13, 2026
Same with us - some clients/tenants fail to load the SPListForm.aspx contents. We cannot reproduce it locally.
TMMetz commentedon Oct 13, 2026
Seeing the same behaviour here. As of now, only our test tenant appears to be affected.
If this update is rolled out to our production tenant, it could have a significant operational impact and would likely cause major disruption.
Update: After opening a ticket MS has confimed this Issue via SP1503038 as a recent API change
23 remaining items
CDH-ADVITA commentedon Oct 14, 2026
2:00 until the next update is also unacceptable. Roll back the change and let us get back to work.
SPJS commentedon Oct 14, 2026
Not sure how they are rolling out the fix since I just got this error on my tenant today!
Alexander
erockwork commentedon Oct 14, 2026
Looks like our tenant is working again.
vladigubler commentedon Oct 14, 2026
BTW, we got first indications regarding the issue from customers around 10:00 AM EST on Monday, so it took 50 hours to handle...
mgordic commentedon Oct 14, 2026
I saw the same message, but so far, nothing has changed in my tenant 🤦
W0ut001 commentedon Oct 14, 2026
Hmm just checked.... (21:20 CET) issue still present on our tenant.
CDH-ADVITA commentedon Oct 14, 2026
Same here. we have at least a dozen reports in the last hour. At what point does Microsoft reimburse for the loss of production??? 50 hours and counting
erockwork commentedon Oct 14, 2026
OK, update on our tenant. Only admins of the tenant can use forms...regular permissioned users still cannot access forms.
W0ut001 commentedon Oct 15, 2026
It works again (7:30 CET). Had to wait a little longer than others.
PauliusBaltrenasFlowForma commentedon Oct 15, 2026
Works on our tenants also. Took a long time to get them working again.
VesaJuvonen commentedon Oct 19, 2026
Seems that the root cause of this issue was the same as with #11059. The issue was detected by the automatic engineering systems, but due to internal complexity disabling the rollout of the new build took longer than expected. Engineering has acknowledged that their internal validation was missing key customer scenarios which is why this issue was not detected earlier. Needed updates are now in progress for the future testing and validation by the right teams.
Thank you everyone for flagging the issue openly here for others to benefit - This helped to speed up the resolution of the root cause. Highly unfortunately situation which should not happen in future, given the updates on the validation processes.
Closing this now as fixed.