Children display macro not updating automatically

[Chris Morphew]

When I add child pages to a parent page (or rename child pages) the macro doesn't update on the parent page. I am definitely publishing the child page and clicking to view the parent page either from the breadcrumb or the left hand nav (so not hitting 'back').

The only way to fix it seems to be editing the parent page, clicking to edit the macro, saving it without making any changes to the macro then publishing the parent page. Obviously this isn't much good as you have to remember to do this every single time you add a new child page.

Any idea how to fix this?

[Joris Vleminckx]

October 2022 and still not fixed :-(

[Gareth Jones]

October 2023 and still not fixed :-(

This bug will be 3 year old next month. I hope Atlassian buy it something nice to celebrate.

[Sova]

Still seeing this behavior with two different client's Confluence instances.  Apparently, Atlassian doesn't care to fix it?

[Mihkel Ronk]

Omg this is still not fixed! C'mon. Need to move here from Notion and crying...

[Nic Brough -Adaptavist-]

Have you tried the tests given already?  

[Mihkel Ronk]

Ok, when checking next day it seems to have updated the list. But I'd still say that it's a bug.

[Bartosz Dopke]

The problem still exists.

[Nic Brough -Adaptavist-]

Have you tried the tests given already?  

[Jaremy Cheetwood]

This issue still exists and I am seeing it regularly where I have to re-publish the pages to get the children pages to update.

[Greg Williams]

Are you using the colon ( : ) in the page title?

I have a user with a similar issue and removing the colon takes care of this

[Nic Brough -Adaptavist-]

Could you do a quick test on timing?  Add a child page as normal, publish it and then leave for a few minutes (make a cup of tea maybe) before clicking back to view the parent.

Is the macro displaying correctly when you now view it?

My logic here is that when you save a page, Confluence builds an index for it.  The macro reads from the index.  The indexing of a page is done after it is updated, and if you've got a big Confluence or it's currently loaded, it might not be happening until after you've gone back to the parent page, so the macro has rendered from old data!

[Bill Bailey]

Well he is on the cloud, so could be a caching issue. Does the macro display properly with CRTL F5 while viewing the page? If so, it is just a delay in replication across the CDN -- sometimes an issue with Cloud apps.

[Chris Morphew]

I'm out for a week now, but I could try the timing thing later.

I did notice that if you refresh the page it fixes the issue rather than just clicking to load it. You may well be right maybe it's a cache thing.

[Jaremy Cheetwood]

Late bump but this still exists.