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
RE: Edit mode loads stale macro context after the context has been updated - #2 by TonyGoughAdaptavist
What you mention is the reason why I was unfortunately unable to find workarounds for this stale macro context issue from my post.
It seems that it is actually standard behaviour for macros to retain their context data from the last page version where they were edited, rather than always have an up to date context for the most recent page version.
If that were not the case, it would be possible to code around the stale-context issue by simply inspecting the context and discarding obsolete versions.
I hope we hear from Atlassian on this