Problem Definition

Forge macros can define an adfExport function that returns ADF for Confluence export flows. Forge function responses have a 5 MB payload limit, so large macro export representations may not fit in the response.

Forge Object Store can store large objects. However, Confluence export currently cannot resolve an Object Store reference included in returned ADF into the referenced content while parsing the ADF. An ADF media node could potentially reference an Object Store URL, but this requires explicit support in the Confluence export pipeline.

Suggested Solution

Provide a supported mechanism for adfExport to return an Object Store reference, or another server-side external-content reference, that Confluence securely resolves during export.

Why this is important

This would allow apps to export large macro representations without truncating the content or converting it to an image. It would also reduce a capability gap for apps migrating large content macros to Forge.

Workaround

Apps can return only part of the content with a link to the complete content, or return an image representation where supported. There is currently no workaround that preserves the complete structured content above the response limit.

Related issue

CONFCLOUD-84936 tracks the related impact on large Forge macro content in Word exports.