Issue Summary

In Confluence Cloud, the Space Settings “Trash” screen (/wiki/pages/viewtrash.action?key=<space-key>) only displays the most recent 500 deleted items, with no visible pagination or “load more” controls. When there are more than 500 items in the space trash, older items cannot be accessed via the UI.

Steps to Reproduce

1 In a Confluence Cloud site, pick any space (e.g. key = CSS).

2 Create at least 500+ pages in that space (e.g. Page 1 to Page 505).

3 Delete all these pages so that they are moved to the space trash.

4 Navigate to the space’s trash:

• Space sidebar → Space settings → Content tools (or equivalent) → Trash, or
• Direct URL: 

  https://<site>.atlassian.net/wiki/pages/viewtrash.action?key=<space-key>

5 Scroll to the bottom of the Trash screen and confirm how many items are listed and whether there is any pagination or “load more” element.

Expected Results

• The trash UI should allow users to browse and access all deleted items in the space, even when the number exceeds 500.

• The UI should provide proper pagination or infinite scroll so that older trashed items (beyond the first 500) can be listed, restored, or purged from the Trash screen.

Actual Results

• The trash UI only lists the most recent 500 items.

• When there are more than 500 deleted items in the space trash, items older than the latest 500 are not visible in the UI at all.

• There is no visible pagination or “load more” control that would allow the user to move to the next page of results.

• As a result, older trashed content cannot be discovered or restored from the UI, and users have to rely on audit logs or API calls to identify and recover specific pages.

Workaround

Currently there is no way to see beyond the first 500 items in the trash UI itself.

 

A customer has requested that the current limitation (maximum of 500 items displayed in the Trash) be explicitly stated in the official documentation.

Since users currently perceive the missing items as a bug or data loss, documenting this behavior as a known limitation would help manage expectations and reduce confusion while this improvement request is being considered.