eazyBI incident
eazybi for Confluence does not include macros in PDF exports
eazyBI experienced a minor incident on August 17, 2026 affecting Web App, lasting 1d 5h. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- identified Aug 17, 2026, 06:45 AM UTC
Starting on Saturday at 17:36 EEST (August 15, 2026), we have disabled the export of eazyBI macros from Confluence pages. The issue is related to the Confluence Forge version, and we are actively discussing a solution with Atlassian.
- monitoring Aug 18, 2026, 07:29 AM UTC
The fix has been implemented, and the Confluence page PDF export, including eazyBI macros, is again enabled starting 10:15 EEST Augst 18, 2026. We continue to monitor.
- resolved Aug 18, 2026, 12:28 PM UTC
This incident has been resolved.
- postmortem Aug 18, 2026, 12:28 PM UTC
After the Confluence Forge upgrade, we received a very large number of export requests that turned out to be invalid: they were not genuine exports but Forge platform calls made during page views and other non-export contexts. To keep the application stable, on August 15 at 17:36 EEST, we stopped all macro exports; this meant eazyBI macros were temporarily not rendered in Confluence page exports. The fix was ready within hours, but we could not publish it immediately: the Forge platform still treated our app as a Connect app and would have turned a minor update into a major version change \(Atlassian acknowledged this as a platform bug\). Once the new Forge version was published successfully, it determines the export type and processes only genuine exports, rendering the macro unchanged in all other cases. On August 18 at 10:15 EEST, we re-enabled exports, and they continue to be processed successfully.