SharePoint Pages Error Unknown Render Failure

[Nez-plt]

What type of issue is this?

Documentation issue / typo

What SharePoint development model, framework, SDK or API is this about?

not applicable

Target SharePoint environment

SharePoint Online

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

• browser version
• SPFx version
• Node.js version
• etc

Issue description

We have a folder named "Documents" in our SharePoint library, and inside this folder, there are 9 subfolders. We're using the filtering feature, but when we select the "All Documents" view during filtering, an error appears on the screen. "Unbekannter Renderingfehler.
n.getAttribute is not a function"
However, when we create a new view named "All Documents." (with a dot at the end), the issue is resolved. The problem is, we have many pages, and this issue occurs frequently, which makes it difficult to manage.

[Ashlesha-MSFT]

Hello @Nez-plt,
Thank you for bringing this issue to our attention. We will look into it and get back to you shortly.

[Ashlesha-MSFT]

@Nez-plt,
We tried to reproduce it with the following steps:

1. Created a folder named "Documents" in a document library
2. Added around 9 subfolders inside it
3. Added a "Category" (Choice) column with values like Internal, External, Confidential
4. Assigned values to subfolders using Grid View
5. Switched to the "All Documents" view and applied a filter

Result:
We couldn't reproduce the error:
"Unbekannter Renderingfehler. n.getAttribute is not a function"

Filtering worked normally, even with that folder/view naming.
Could you please confirm:

• Is "All Documents" customized (grouping, formatting, etc.)?
• Are the metadata values applied to folders, documents, or both?
• Are there any custom scripts, view formatting, or Power Automate flows?
• Does the error appear in modern SharePoint, classic, or Teams view?
• Can you share a screenshot or browser console output?

This will help us isolate the issue. It does look like a platform-level bug, but we’ll need a bit more detail to confirm.

[Nez-plt]

Hi,
Is "All Documents" customized (grouping, formatting, etc.)? Yes
Are the metadata values applied to folders, documents, or both? Metadate vaules applied to both.
Are there any custom scripts, view formatting, or Power Automate flows? I guess yes, to be sure where can i check ?
Does the error appear in modern SharePoint, classic, or Teams view? Sharepoint Modern
in attached you can also find the list of filter. there if i chosse "email tabellarisch" getting an error. I have created e-mails - tabellerisch. and there all works fine.

[Ashlesha-MSFT]

@Nez-plt,
We’ve attempted to reproduce the issue under general conditions, and it did not occur in our environment. However, now that we know customization and specific metadata values are involved, it’s possible this is a view formatting/rendering bug related to certain string patterns or malformed custom code.

We’re escalating this to our engineering team with these details and will keep you updated once we hear back from them.

Thanks for your patience!

[Nez-plt]

Thank you, I’ll wait for your response.

[Ashlesha-MSFT]

Thanks for raising this. However, this is not a development issue, so it doesn't belong in the SharePoint Developer Docs GitHub repository.
We’ll be closing this issue with the label type:invalid-not-dev-issue.
For issues related to out-of-the-box Microsoft 365 features (like list validation behavior), please use the Microsoft 365 Admin Support channel instead. Only tenant admins can raise such issues via the Admin Center.
How to report via Admin Center:
1. Go to https://admin.microsoft.com/
2. Navigate to Support > New service request
3. Clearly describe the issue (include screenshots, URLs, browser details, and steps to reproduce)
4. Submit the request — the system will route it to the appropriate support team
Microsoft guidance: https://learn.microsoft.com/microsoft-365/admin/get-help-support?view=o365-worldwide
Thanks for your understanding!

[Nez-plt]

We di alreday, They do not have solution, they have just workaround solution like create new view