Workflows for Confluence - Macros showing with "Broken macro" message

Update timeline

1. identified Apr 15, 2026, 03:58 PM UTC

   We're aware that some customers are seeing intermittent "Broken macro" errors with Workflows macros, and we understand how disruptive this is. * What's happening As part of a required platform migration within Confluence (from Connect to Forge), some older macros are not being routed correctly by Confluence's infrastructure. Instead of calling the current Workflows Forge app, Confluence is still attempting to call the legacy Connect extension, which produces the error. * What we're doing AppFox is working directly with Atlassian to permanently resolve this. We will update this notice as progress is made. * Workaround Atlassian have provided a workaround: edit the affected page, remove the macro, re-add it, and save. This forces Confluence to update the macro reference so it routes correctly. We understand this may not be feasible for customers with many affected pages. Atlassian have offered to perform this remediation in bulk. Please contact us and we will facilitate. Affected conditions - Only the Workflows Status and Workflows Metadata macros are affected. - Only macros created prior to the Forge migration in Q4 2025 (or created from older templates). - Most commonly occurs when: (1) a Workflows macro is included in a Content Properties Report macro, or (2) a page is exported via the REST API (including by third-party apps such as Scroll PDF Export). - On standard Confluence page views, the error may appear briefly before the page automatically re-renders correctly.