Issue Summary

When pages contain a large number of macros, the Confluence renderer triggers a backend Forge invocation for each macro, causing apps to hit the Forge invocation rate limit. This results in performance issues, negative user experience (e.g., infinite spinners), and is a blocker for partners migrating from Data Center to Cloud.

Steps to Reproduce

1. Create a Forge macro (UI Kit or Custom UI) with the adfExport property defined in the manifest.

1. Add a large number (e.g., 100+) of these macros to a Confluence page, including inline macros.

1. Attempt to export the page to PDF or Word, or simply view the page.

1. Observe the export output and macro loading behavior.

Expected Results

Pages with many macros do not hit Forge invocation rate limits, and all macros load and export successfully for end users.

Actual Results

When pages contain many macros, each macro triggers a backend Forge invocation, quickly hitting the invocation rate limit.Users and partners report negative customer impact, migration blockers, and business risk due to these limitations. 

Workaround

Currently there is no known workaround for this behavior. A workaround will be added here when available