I am using the Content Properties Report macro on one of my organization's confluence pages.
I have 5 different pages that have content properties tables to pull into this report. However, only 4 pages are showing.
I have the report filtered by a specific label:
I have confirmed that the missing page uses the same label as the above (and that it matches the 4 other pages that are showing in the report)
Specific note that this page was created in 2020, so I don't know if that has any effect on the macro
Hello @Christy Kennedy
Given the timing, I would definitely retest this after yesterday’s incident before digging too deep into page age or macro behavior.
Atlassian had a Confluence search incident on April 8, 2026, and during recovery they explicitly said some customers could still see delays for recently indexed data. That does not prove this is the cause here, but it is close enough to your timing that I would not ignore it.
Content Properties report is driven by the page having the correct label, and if you use it, the correct Content Properties ID as well. Atlassian also notes that the macro expects one header row or one header column, not both.
It could be related to Automatic Migration from Legacy Editor.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.