Page Status Report Failed to Update after Handy Page Status was applied to Additional Pages

[Anne Hildebrand]

Today I was testing out the Page Status Report but I noticed that the report failed to update after additional Confluence pages had the Handy Page Status applied to them. I even clicked the browser refresh button several times but still was unable to see the complete list of pages on the report. What is causing the issue?

[Radwan Almsora · Accepted solution]

don't forget to click the Accept Solution button

[Tomislav Tobijas · Accepted solution]

Hi @Anne Hildebrand ,

Is it just showing a partial list, or is it displaying "No content found"? I'm asking as there's a known bug around this: CONFCLOUD-81728: Page Property Reports in Confluence Show "No Content Found" Intermittently 

Actually, I just came by to say to maybe reach out to the vendor as well. If we're talking about this app, you can find support channels in the "Support" tab.
Potentially, they could also help troubleshoot this and maybe check with Atlassian why it's breaking the native macro 👀

Cheers,
Tobi

[Anne Hildebrand]

Hi Tobi,

It showed a partial list when I was using the refresh button. Once I closed the page and returned to the Page Status Report page I was able to see the full list. 

Thank you,

Anne

[Tomislav Tobijas]

Cool. Glad you managed to sort it out. Thanks for sharing the resolution and what worked! 🙏

[Radwan Almsora · Accepted solution]

The Page Status Report fails to update immediately because Confluence Cloud indexes macro data asynchronously, which creates a slight backend sync delay after applying or changing a status. Simply refreshing your browser does not force Confluence to re-index the newly added statuses right away.

Why This HappensBackend Indexing Lag: Confluence relies on its search index to compile data for dynamic reports (like the Page Status Report or Page Properties Report). When you add a new Handy Page Status to a page, it can take anywhere from 30 seconds to a few minutes for the Atlassian backend to parse and push that metadata into the report.

Browser Cache Limits: Clicking the browser refresh button only reloads the current page view; it cannot force Confluence to speed up its search indexing pipeline.

I belive this was answered here: 

Page Properties Report Macro Delay in Confluence Cloud Live Edit Mode

[Anne Hildebrand]

Hi Radwan,

This seems to make sense according to what I experienced. I know another user experienced the same issue so I will pass along this information. I appreciate you sharing the link too.

Thank you,

Anne