Issue Summary

When Connect macro is just migrated to Forge, i.e. while in ADF format its extensionType is still com.atlassian.confluence.macro.core, adfExport for this macro is invoked every time the page renders. This doesn't happen when for a pure Forge macro.

Steps to Reproduce

1. Have an app with a macro that has defines adfExport function.
2. Create a new page with this Forge macro.
3. Update page ADF so that:
   • extensionType is com.atlassian.confluence.macro.core instead of com.atlassian.ecosystem.
   • extensionKey is a macro module key, instead of full Forge macro key.
4. Refresh the page.

Expected Results

adfExport function is not invoked.

Actual Results

For a brief moment (especially noticeable on slow network), a result of an adfExport function appears in place of a macro, then the regular macro content is rendered. adfExport function is invoked. This doesn't happen for a pure Forge macro.

Workaround

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