-
Type:
Suggestion
-
Resolution: Unresolved
-
Component/s: Macros - Page Properties
-
1
-
2
Hi everyone,
This is Erik from the Confluence team. Thank you for all the thoughtful comments on the Page Properties Report macro and the challenges you're seeing with large datasets.
A quick clarification on limits: Confluence Data Center documents has a configurable limit of 3,000 pages for this macro (https://confluence.atlassian.com/doc/page-properties-report-macro-186089616.html). Confluence Cloud does not publish the same explicit limit as the macro's architecture has changed (https://support.atlassian.com/confluence-cloud/docs/insert-the-page-properties-report-macro/).
In practice, very large reports can still hit performance or reliability limits, which is why we’re treating this as a product improvement rather than a single “bug fix” with a one-size-fits-all answer.
For Cloud today, the workaround is to split up the dataset or, where it fits your workflow, use Confluence databases as an alternative: https://support.atlassian.com/confluence-cloud/docs/get-started-with-confluence-databases/
We understand there is a lot of interest in this feature, so I have converted this Bug into a Suggestion so your comments and votes will carry over and you can continue to track our progress.
Please share any additional information about your particular use case that you think would help us prioritise building this feature.
Best,
Erik
Issue Summary
The Page Properties Report (PPR) macro in Confluence Cloud does not reliably return complete, consistent results when operating on large datasets (~1,500+ pages). Each page refresh can yield a different number of rows and a different subset of pages, making the macro untrustworthy for governance and reporting purposes.
The issue exists at the PPR macro level itself — it reproduces even with a single PPR macro on a page and a smaller dataset (~70 pages). The problem is amplified when multiple PPR macros are present or when nested inside third-party macros (e.g., Table Toolbox).
The customer's dataset (~1,500 pages) is well within the PPR's designed maximum of 3,000. The macro should handle this reliably without requiring workarounds like splitting into multiple date ranges or separate macros. The customer's space is actively growing and they will soon need additional PPR macros, making this increasingly urgent.
Steps to Reproduce ( Reproducible on customer' site)
Scenario A
- Create a Confluence Cloud space with a large number of pages (~1,500+), each containing a Page Properties macro with the same label (e.g., properties-report).
- Create a page with a Table Toolbox macro containing two Page Properties Report macros, each filtered by the same label but with different date ranges (e.g., 2014-2023 and 2014-present).
- Publish the page.
- View the page and note the row count and listed pages.
- Refresh the page multiple times.
Scenario B (without Table Toolbox):
- In a Confluence Cloud space, ensure ~70+ pages exist with the same label (e.g., topic_card).
- Create a page with a single Page Properties Report macro filtered by that label.
- Refresh the page multiple times.
- Observe that the row count varies between refreshes (e.g., 55, 57, 65, 70).
Expected Results
The Page Properties Report macro should return a stable, consistent, and complete list of matching pages on every page load/refresh.
Actual Results
Each refresh returns a different number of rows. Observed examples from the customer's page:
| Refresh | Count displayed | Rows in table |
|---|---|---|
| 1 | 1341 | 1539 |
| 2 | 1342 | 1540 |
| 3 | 1540 | 1540 |
| 4 | 1541 | 959 |
| 5 | 1541 | 1157 |
| 6 | 1541 | 1541 |
The issue persists across browsers (Chrome, Edge) and users. Sometimes the macro shows "Error rendering macro" or fails silently with no data returned. The problem is intermittent and has been ongoing
- The customer’s space currently has ~2,000 pages, >1,500 with Page Properties, and the report is used for weekly and quarterly governance checks.
- “This makes the Page Properties Report macro unsuitable as a source of truth for governance dashboards, audits, and SME reporting.”
Workaround
- Splitting large Page Properties Reports into smaller datasets (e.g., shorter time ranges or fewer source pages).
- Placing them in separate Table Toolbox macros instead of nesting multiple large PPRs inside a single one.