I’ve a weird behavior that showed up today/this week.
The macros from a Forge Developer environment are now showing up in the Confluence editor.
Pages that have already have the macro work. However, the macro fails in edit mode. And it does not show up in the Macro list.
This behavior shows in different apps. I tried two different apps and two different cloud sites, and in both the Macro’s do not show up in the editor.
Anyone experience the same issue?
Update: Staging is also affected.
Update: Seems to be mostly the case in Firefox. There it is reliably not showing up.
I’m pretty sure I saw the issue in Chrome as well, but seems to work again atm.
Hello @RomanStoffel, we have identified 4 problems related to macros on 3 of our apps and already opened a support ticket.
These are the problems we identified:
“Error Loading extension!” message showing as the body of the macro when editing the page
Not being able to find the specific macro when trying to insert with / ← This issue degraded over time as at the beginning the workaround to refresh the browser used to work but now it no longer does
Not being able to edit the macro
UI Kit macro not rendering with console error: Uncaught Error: vfm/components/embedded-file-view missing confluence ← This is likely related to ADFRenderer component from UI Kit, since it’s the only thing we’re using in this macro. This is the only issue we’ve reproduced on staging.
In our case, none of the apps is yet on production, some of the issues affect only development environments, but there is one affecting staging too. All the issues were identified using chrome.
Yeah, in one of our apps we have two different macros, one of them shows this message and the other doesn’t. The one that does show it is in UI Kit and the one that works is in Custom UI, but for other apps the Custom UI macros are also affected, so, it’s kind of random.
This is from Atlassian in a support thread, but it’s obviously AI, so take with a pinch of salt as to whether it’s accurate:
What’s happening:
This is a known platform-level bug that affects apps which have recently migrated from the Connect framework to Forge (such as draw.io and Mosaic/Kolekti). The issue lies in how Confluence resolves the older Connect macro references stored in your pages against the newer Forge version of the apps. Essentially, the system fails to correctly map the old macro format to the new Forge extension, which causes:
The “Error loading the extension” message on existing diagrams
The inability to find the draw.io macro via the / command in the editor
This is not related to your DC-to-Cloud migration, and it explains why both draw.io and Mosaic are exhibiting the same behavior — they’re both affected by the same underlying platform issue.
Well, it doesn’t look like a Connect to Forge migration issue to me since one of our apps does not have a Connect counterpart … Well, it actually does, but since it’s a quite big app and refactoring needed to make it a “Runs On Atlassian” app is large, the team in charge of the refactoring is treating it as a new app, while other team keeps working on the Connect on Froge app in the meantime. So appId / appKey are not matching for this one, but that means the macros are also treated as new macros.
We are aware of this issue and can confirm it is affecting multiple Forge apps with macros in Confluence. Our engineering team is actively investigating.
This is being tracked as an active incident — you can follow live updates here:
