Issue Summary

When a dynamicContentMacro is present in the Confluence page and the macro’s height exceeds a certain value (e.g. cannot fit on a single PDF page), the first page of the pdf export will be left blank. The macro and the rest of the export is still present in the PDF, but they’ll be pushed to the second page due to the first page being completely blank.

Steps to Reproduce

1. Create a Connect app that uses a dynamic content macro on a page and make it larger than one page of a PDF.
2. Export the page to PDF and download the PDF.
3. The PDF will contain a blank page at the beginning, with the content being pushed to the second page.

Expected Results

The macro content in the first page.

Actual Results

The macro content is pushed to the second page, having the first page blank.

Workaround

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