SharePoint library does not show files when grouping is enabled and Collapsed

Question

SharePoint library does not show files when grouping is enabled and Collapsed

Mayur Rana 25

We've several libraries where grouping is enabled and by default they are collapsed. No files are displayed in these libraries. When we change the view setting for Grouping to Expanded from Collapsed then all files are visible.

The number of files in each of these libraries are less than 2000 files.

Dylan Flowers 15 Reputation points

2026-07-10T18:06:40.01+00:00

Hi there,

I'm commenting to report that the same issue began occurring within our organization at the exact same time as this post was created. Library groupings were working fine on June 8th and began to fail on June 9th. It seems to be an issue isolated to views using nested groupings (i.e. using a secondary column in 'group by'). This is affecting multiple SPO sites within our org, all with consistent cause and effect. Our global admin is aware of the issue but is operating under the assumption that this is a wider-spread issue and not isolated to our organization.
Catherynne Mattar 0 Reputation points

2026-07-13T04:12:22.21+00:00

We've had the same problem - it seems to happen if you're trying to group by multiple columns, eg. group by Col1, then by Col2. That used to work, but something's changed very recently and now you can only group by one column. Which is not great...
David Saynor 0 Reputation points

2026-07-13T07:23:13.49+00:00

We are having the same issue, and it is most frustrating. As a temporary resolution we are changing the settings to Expanded as opposed to collapsed.
Penney, Susan 0 Reputation points

2026-07-13T08:31:59.5033333+00:00

Same is happening for me to. Document libraries with grouped views no longer render when trying to expand the group. Was working last week.
Flavio Krahl 0 Reputation points

2026-07-13T08:52:06.21+00:00
I encountered the same issue today. Here are some insights i gathered that might help resolve the issue:

It does not occur on every Sharepoint site (at least for me)

In classic view, using built in fields for nested grouping, the second group is displayed like this:

AuthorAuthor : (undefined)

If using nested grouping but selecting the "expanded" version as default, only one group is displayed, but all the items inside are displayed correctly.

Field type or grouping order has no impact at all on the issue. As soon as you try to group by any 2 fields it occurs.

The issue persists sitewide across all Lists.

Site settings have been thoroughly checked and no differences noted between a working and a corrupted site, so it is most likely a backend problem.

Workaround: Use only one grouping field until the issue is resolved by Microsoft and/or your company IT department (seems to occur only in business accounts/sites since my private Sharepoint lists all work fine)

Hope this helps everyone having this issue and Microsoft resolving it.
Ralf Weyer 0 Reputation points

2026-07-13T12:35:56.76+00:00

Coming back after two weeks vacation this issue has shown at least on one of the SharePoint sites I'm owner off in the company I work. The pattern is similar tow what others have reported above, on this particular SP we save different CAB protocols in different document libraries depending on the particular CAB, and in these libraries the files are grouped first by year and afterwards by month.
When the library is set to "Expanded" in "Group By" all the fiels are shown, unfortunately only grouped by year and not by months in the years anymore, so this is not a real solution. But when this setting is set to "Collapsed" the library only shows the years, and I'm not able to expand the years to show the months and the files within the months.
Brad Bateman 95 Reputation points

2026-07-13T15:51:07.8033333+00:00

There is a known issue for this now in the Microsoft 365 admin center. https://admin.cloud.microsoft/?#/servicehealth/:/alerts/SP1425697

Some users' document libraries and list views using multiple group filters may not display results in SharePoint Online

Issue ID: SP1425697

Affected services: SharePoint Online

Status: Service degradation

Issue type: Incident

Start time: Jul 13, 2026, 2:42 AM EDT

User impact

Users' document libraries and list views using multiple group filters may not display results in SharePoint Online.

More info

Specifically, impacted users report that document libraries and list views using both Primary and Secondary grouping may not display the full or expected results.

Scope of impact

Some users attempting to view document libraries and list views using multiple group filters may be impacted. This information may be updated as our investigation continues.

Current status

Jul 13, 2026, 7:25 AM EDT

We’ve identified that a recent change to the service component responsible for rendering grouped views in SharePoint Online document libraries and lists is causing impact. We’ve developed a fix and are validating that it resolves the issue while we determine the safest deployment approach.

Next update by:

Monday, July 13, 2026 at 1:00 PM EDT
Jamuna 0 Reputation points

2026-07-13T18:11:01.1166667+00:00
We are experiencing the same issue across multiple SharePoint Online document libraries.

Issue:

Libraries use two levels of grouping (Category → Subcategory).

When the view is configured with groups Collapsed by default, expanding the first group does not display the second-level groups or documents.

When the same view is changed to Expanded by default, all documents are visible.

Testing completed:

Confirmed the documents and metadata still exist.

Reproduced the issue in multiple existing SharePoint sites.

Reproduced the issue in a brand-new test library with sample data.

Tested with indexed choice columns.

Single-level grouping works correctly.

The issue only occurs when using two grouping levels.

Same behaviour is present in both Modern and Classic experience.

In Classic experience, expanding the first group sometimes displays "Working on it..." and the nested groups never load.

Additional information:

Users reported the issue started over the weekend.

We have not identified any recent library configuration changes.

The issue appears to affect multiple libraries and sites, not a single SharePoint library.

Has Microsoft identified this as a service issue or regression, and is there a known workaround other than setting grouped views to Expanded?

Any guidance would be appreciated. Edited:Its fixed today,I think Microsoft fixed it.

6 answers

Your answer

Dylan Flowers 15 Reputation points

2026-07-10T18:06:40.01+00:00

Hi there,

I'm commenting to report that the same issue began occurring within our organization at the exact same time as this post was created. Library groupings were working fine on June 8th and began to fail on June 9th. It seems to be an issue isolated to views using nested groupings (i.e. using a secondary column in 'group by'). This is affecting multiple SPO sites within our org, all with consistent cause and effect. Our global admin is aware of the issue but is operating under the assumption that this is a wider-spread issue and not isolated to our organization.
Catherynne Mattar 0 Reputation points

2026-07-13T04:12:22.21+00:00

We've had the same problem - it seems to happen if you're trying to group by multiple columns, eg. group by Col1, then by Col2. That used to work, but something's changed very recently and now you can only group by one column. Which is not great...
David Saynor 0 Reputation points

2026-07-13T07:23:13.49+00:00

We are having the same issue, and it is most frustrating. As a temporary resolution we are changing the settings to Expanded as opposed to collapsed.
Penney, Susan 0 Reputation points

2026-07-13T08:31:59.5033333+00:00

Same is happening for me to. Document libraries with grouped views no longer render when trying to expand the group. Was working last week.
Flavio Krahl 0 Reputation points

2026-07-13T08:52:06.21+00:00

I encountered the same issue today. Here are some insights i gathered that might help resolve the issue:

It does not occur on every Sharepoint site (at least for me)

In classic view, using built in fields for nested grouping, the second group is displayed like this:

AuthorAuthor : (undefined)

If using nested grouping but selecting the "expanded" version as default, only one group is displayed, but all the items inside are displayed correctly.

Field type or grouping order has no impact at all on the issue. As soon as you try to group by any 2 fields it occurs.

The issue persists sitewide across all Lists.

Site settings have been thoroughly checked and no differences noted between a working and a corrupted site, so it is most likely a backend problem.

Workaround: Use only one grouping field until the issue is resolved by Microsoft and/or your company IT department (seems to occur only in business accounts/sites since my private Sharepoint lists all work fine)

Hope this helps everyone having this issue and Microsoft resolving it.
Ralf Weyer 0 Reputation points

2026-07-13T12:35:56.76+00:00

Coming back after two weeks vacation this issue has shown at least on one of the SharePoint sites I'm owner off in the company I work. The pattern is similar tow what others have reported above, on this particular SP we save different CAB protocols in different document libraries depending on the particular CAB, and in these libraries the files are grouped first by year and afterwards by month.
When the library is set to "Expanded" in "Group By" all the fiels are shown, unfortunately only grouped by year and not by months in the years anymore, so this is not a real solution. But when this setting is set to "Collapsed" the library only shows the years, and I'm not able to expand the years to show the months and the files within the months.
Brad Bateman 95 Reputation points

2026-07-13T15:51:07.8033333+00:00

There is a known issue for this now in the Microsoft 365 admin center. https://admin.cloud.microsoft/?#/servicehealth/:/alerts/SP1425697

Some users' document libraries and list views using multiple group filters may not display results in SharePoint Online

Issue ID: SP1425697

Affected services: SharePoint Online

Status: Service degradation

Issue type: Incident

Start time: Jul 13, 2026, 2:42 AM EDT

User impact

Users' document libraries and list views using multiple group filters may not display results in SharePoint Online.

More info

Specifically, impacted users report that document libraries and list views using both Primary and Secondary grouping may not display the full or expected results.

Scope of impact

Some users attempting to view document libraries and list views using multiple group filters may be impacted. This information may be updated as our investigation continues.

Current status

Jul 13, 2026, 7:25 AM EDT

We’ve identified that a recent change to the service component responsible for rendering grouped views in SharePoint Online document libraries and lists is causing impact. We’ve developed a fix and are validating that it resolves the issue while we determine the safest deployment approach.

Next update by:

Monday, July 13, 2026 at 1:00 PM EDT
Jamuna 0 Reputation points

2026-07-13T18:11:01.1166667+00:00

We are experiencing the same issue across multiple SharePoint Online document libraries.

Issue:

Libraries use two levels of grouping (Category → Subcategory).

When the view is configured with groups Collapsed by default, expanding the first group does not display the second-level groups or documents.

When the same view is changed to Expanded by default, all documents are visible.

Testing completed:

Confirmed the documents and metadata still exist.

Reproduced the issue in multiple existing SharePoint sites.

Reproduced the issue in a brand-new test library with sample data.

Tested with indexed choice columns.

Single-level grouping works correctly.

The issue only occurs when using two grouping levels.

Same behaviour is present in both Modern and Classic experience.

In Classic experience, expanding the first group sometimes displays "Working on it..." and the nested groups never load.

Additional information:

Users reported the issue started over the weekend.

We have not identified any recent library configuration changes.

The issue appears to affect multiple libraries and sites, not a single SharePoint library.

Has Microsoft identified this as a service issue or regression, and is there a known workaround other than setting grouped views to Expanded?

Any guidance would be appreciated. Edited:Its fixed today,I think Microsoft fixed it.

Answer 1

Perri Lamanna 0

Update on our lists; the collapsed grouped views are now expandable.

The "fix" deployment by MSFT appears to have been successful.

0 comments

Answer 2

Dear all,

I'm sorry for the delay responding.

From what I’m currently observing on the community forum, I’ve also received similar reports from other users experiencing this behavior.

At this time, there has been no official announcement, service advisory, or confirmed fix published by Microsoft. As community moderators, I don’t have access to internal service logs, backend diagnostics, or engineering dashboards due to privacy and security restrictions. Issues that may involve backend or service-related problems can only be fully investigated and resolved by Microsoft’s product engineering teams.

The only channel that connects directly to those engineering and service teams is the Microsoft 365 Admin Center. For this reason, I strongly recommend contacting your Microsoft 365 administrator and asking them to report the issue through the Admin Center, as this helps Microsoft track, prioritize, and investigate service-related problems more effectively.

Please contact your admin to report the issue in the Microsoft admin center. Your Admin should go to the admin center then choose service health, and report an issue.

User's image

I truly appreciate your patience and understanding while this is being looked into. I’m hopeful that this will be addressed in an upcoming update.

Please feel free to reach out if you notice any changes or need further assistance, I’ll be here to help.

Answer 3

Perri Lamanna 0

Site user is experiencing same issue in a list using collapsed grouping.

Reported by user just this afternoon. Testing and confirmed.

Groups in views range from 7 items to over 1000 (in different views).

Temporarily changing grouping to expanded for users convenience until this is resolved.

0 comments

Answer 4

Mayur Rana 25

Hi Henry,

thanks for your reply.

See my response below.

Does this behavior occur in a single SharePoint library or across multiple libraries/sites? - in all libraries where we have grouping enabled.
Is the issue affecting all users who access these libraries, or only specific users? - all users
Are the files missing only when the groups are collapsed, and then appear immediately when you switch the grouping setting to Expanded?- As soon as view is modified to Expanded, all files are visible. When group view is Collapsed, files are not visible.
What column(s) are being used for grouping in the affected view? Mostly Single Selection / Choice column
Does the issue occur in all library views or only a specific custom view? Custom view and All Documents default view
Are you using the modern SharePoint experience or the classic experience? - Modern
Have there been any recent changes to the library, view settings, metadata, permissions, or content structure before the issue started? No changes were made
Could you share a screenshot of the library view when the groups are collapsed, along with the view settings for the grouping configuration?

Mayur Rana 25 Reputation points

2026-07-09T15:48:08.7133333+00:00

Screenshot 2026-07-09 114413.png

In the above screenshot, the highlighted one is expanded but no files are shown. And when clicked on that, it says the folder is empty.Screenshot 2026-07-09 114708.png
Henry-N 16,325 Reputation points Microsoft External Staff Moderator

2026-07-10T14:29:11.69+00:00

Hi @Mayur Rana,

Thank you for your response.

To resolve this issue, Microsoft’s support team will need to be engaged. A technical support engineer can conduct a remote session to investigate the situation, verify backend configurations, and run any required synchronization tools. Since this case will likely involve collecting and analyzing logs, it is recommended to raise a support ticket to ensure a smoother and more efficient resolution process.

The Global Admin should create a service request with Microsoft support to get advanced technical assistance and diagnostics. For detailed instructions on how to get support, please refer to Get support - Microsoft 365 admin.   

If you’re unsure who the Global Admin is within your organization, you can find guidance on locating them here: How do I find my Microsoft 365 admin? - Microsoft Support.  

As community moderators, I don’t have access to internal service logs, backend diagnostics, or engineering dashboards due to privacy and security restrictions.

Thank you again for your time and understanding.

Answer 5

Hi @Mayur Rana,

Thank you for posting your question in the Microsoft Q&A forum.

To better understand the issue and help narrow down the cause, could you please provide a few additional details?

Does this behavior occur in a single SharePoint library or across multiple libraries/sites?
Is the issue affecting all users who access these libraries, or only specific users?
Are the files missing only when the groups are collapsed, and then appear immediately when you switch the grouping setting to Expanded?
What column(s) are being used for grouping in the affected view?
Does the issue occur in all library views or only a specific custom view?
Are you using the modern SharePoint experience or the classic experience?
Have there been any recent changes to the library, view settings, metadata, permissions, or content structure before the issue started?
Could you share a screenshot of the library view when the groups are collapsed, along with the view settings for the grouping configuration?

This information will help us determine whether the issue is related to the view configuration, a rendering problem, or another SharePoint-specific behavior.

Thank you again for your time and understanding. I really appreciate your patience, and I’m here to help. Looking forward to your response.              

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread