Thanks @marc . It is indeed looks like the same issue. Issues’ ‘low’ priority doesn’t sound very promising. Will have to use a hacky way to overcome it for now.
Doing some more digging I found more related topics:
We are experiencing an issue with outdated/stale context variables.
When a user adds a checkbox to a page ([]), and toggles the checkbox, the document version is incremented.
When a macro is on the same page and Confluence does a call to the macro host page after a checkbox is toggled, the req.context atlassian-connect-express is getting still shows the content.version from before the checkbox was updated. It seems that a checkbox toggle does not result in the req.context inside the macro bei…
The following steps reproduce an issue which impacts Confluence user experience and prohibits implementing key functionality when developing macros. The bug produces old, stale macros which are momentarily rendered when they should not be.
Create a basic connect app which includes the following Dynamic Content Macro. This test macro includes a parameter to more closely recreate what would happen with an actual production app macro.
{
"key": "bananamacro",
"name": {
"value": "Banana"
},
"url":…