Issue Summary

When exporting a custom Macro to PDF, Confluence adds a spinner to the export service while the macro content is loading. In some cases, it's possible that the export service will export the page before the content is fully loaded, and that causes the PDF to render the spinner instead of the macro content.

Steps to Reproduce

1. Implement a Forge Macro
2. Add it to a page, and export it to PDF

Expected Results

The macro content is consistently rendered in the PDF file

Actual Results

Randomly, the PDF file will render the spinner instead

Workaround

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