Summary

When migrating a Confluence macro from Connect to Forge, there is currently no way to render large or high-fidelity macro content in Word export or in third-party exporters (e.g. Scroll PDF Exporter). Unlike PDF — where a Forge macro can return null from adfExport and fall back to the high-fidelity Puppeteer/iframe rendering — Word and third-party export paths can only use the adfExport output. This is a regression from Connect, where macros could tailor output per context via renderModes.

Background / current behavior

• PDF works well: returning null from adfExport triggers the Puppeteer render, giving output nearly identical to the live macro.
• Word has no such fallback: adfExport (ADF → OpenXML) is the only supported path. Atlassian has confirmed Puppeteer cannot be used for Word because Word needs a structured document format.
• Because adfExport runs as a synchronous Forge function invocation, its response is bound by the AWS Lambda ~6 MB response limit (~4–5 MB usable). Large macro content (e.g. big tables, ~14 MB ADF) therefore cannot be exported to Word at all — the invocation fails with "Function response size is too large" and the macro silently drops from the exported document.

Impact

• Apps migrating from Connect to Forge lose Word export fidelity for any non-trivial macro — a customer-visible regression.
• For content-heavy macros (tables, reports, snapshots), Word export is effectively broken above the ~5 MB adfExport ceiling, with no workaround.
• Affects enterprise customers who rely on Word/third-party exports of Confluence pages containing these macros.