@alessandrodistefano and @UlrichKuhnhardtIzym1 Thank you very much for the report. The team is investigating this now.
1 Like
Same for us… right now we have to disable that specific code path and let the user publish the page once.
1 Like
Hey all!
Thanks for letting us test this! I’ve noticed a couple of issues with bodied macros.
The first is that there is a slight delay between editing content within the bodied macro, selecting “Done Editing,” and the content of the page updating. This leads to our bodied macros rendering before the content of the page is fully saved.
We use a multi-macro model for our tabs, meaning the first tab in the group collects the content of the other tabs and renders them all together. The other tabs then resize to be as small as possible on the page.
In a scenario where a user adds multiple tabs to a page, selects “Done Editing” on the first tab (which triggers the rendering of the entire tab group), then edits the content of the second tab and clicks “Done Editing” there, the first tab has no way of detecting the change and updating its content accordingly.
From this, I have a couple of requests:
- Would it be possible for us to listen for the “Done Editing” event?
- Would it be possible to minimize the size of the container once the user has finished editing the content of the bodied macro? (This would be useful for our multi-macro model, where only one of the macros in the group renders the content, and the other macros remain hidden)
Thanks again
2 Likes
Hi all!
Thank you so much for your continued testing & feedback.
I wanted to bring everyone in this thread’s attention to RFC-83: Live Docs & Pages in Confluence Cloud
Based on feedback we’ve gotten from developers & customers that have tried Live Docs in this EAP phase, we have an updated RFC for how we see Live Docs evolving in the future, both for end users and developers, and we would love for you to read & give your input.
Again, here is the link! RFC-83: Live Docs & Pages in Confluence Cloud
Cheers,
David
We got the suggestion to use AP.confluence.getMacroBody to check if that works with LivePages to get the macro body content. However, that API seems to have the same issue: As soon as the macro is edited but not published, it does return no content. Breaking our macro in Live Pages view.
For ‘classic’ pages we show a infobox telling the user the content will show up once the page is published. But with live pages you do will now publish them.
Update: The AP.confluence.getMacroBody seems to work now. Either we made some subtle mistake or it got fixed/adapted for live pages. Not sure.
So, that means we most likely fix our macro with that API.
1 Like
We still have this issue with our app in Live Page.
In edit, the app displays a message asking the user to publish.
Once in display mode, we are able to query the API to retrieve the macro content.
In live page, whatever we try, we always receive this error from API:
/rest/api/content/{pageId)/history/{version}/macro/id/{macro-id}
com.atlassian.confluence.api.service.exceptions.NotFoundException: No macro found on content id : ContentId{id=129433601} with version: 1 and macroId: f9a61962-0b55-408d-a34e-8e385cfc0f6b
Can someone please advise what to do?
Thanks!
1 Like
From our experimentation, the REST API for macro content is useless in live pages, at least for a Connect app.
It never finds the macro content. (Speculation, its out of sync or ignores unpublished content)
So, we adopting our app to use the frontend API AP.confluence.getMacroBody. If you actually have to do some background processing on the macro body, I guess your out of luck. And push Atlassian to ‘fix’ the issue. 
2 Likes
did you guys found a fix for this ?
Hi all!
Since this post is outdated (and we have a newer post here: Please test & update your Confluence Cloud apps to function in Live docs by May 30, 2025), we will be locking this thread. Please direct any further conversation in the newer post.
I will also be posting an update there about some of your questions re: fetching macro content via API.