Issue Summary

Customers are experiencing distinct problems with Forge Confluence macro module macros. While one tenant is faced with a panel saying “The metadata-macro is not supported. Raise a ticket” the other is seeing a panel with a “Broken macro” message.

Steps to Reproduce

To replicate the problem, create a content properties report and copy old versions of the affected macros (in the old connect storage format) into the content properties macro.

Expected Results

The actual macro should be rendered.

Actual Results

Customers are faced with a panel saying “The metadata-macro is not supported. Raise a ticket” or a panel with a “Broken macro” message.

Workaround

Manually editing and saving the affected pages to upgrade the macro storage format to Forge format resolves the issue, but it’s not feasible to customers with macros across 1000+ pages.