Issue Summary

On Confluence Cloud pages migrated from the Legacy editor, some legacy Chart macros (`ac:name="chart"`) intermittently fail to render in the modern Fabric renderer and show an error like:
**

Batch update returned unexpected row count from update ...

**
Other charts on the same page may render correctly. This has been reproduced on internal testing sites and confirmed as a rendering bug in the Fabric renderer with the legacy Chart macro. The issue is purely visual (no data loss or corruption).

Steps to Reproduce

1. Open a Confluence Cloud page that was originally created in the Legacy editor and contains one or more legacy Chart macros (`ac:name="chart"`), now opened in the Cloud (Fabric) editor.
2. View the page in read-only mode and observe the chart macros; optionally, hard-refresh the page several times (3–4 times) to see intermittent behavior. 

Expected Results

All legacy Chart macros on the page should render consistently in read-only mode without errors in the Fabric renderer.

Actual Results

Some legacy Chart macros fail to render and display an error similar to:

HHH000315: Exception executing batch [org.hibernate.StaleStateException: Batch update returned unexpected row count from update [0]; actual row count: 0; expected: 1; statement executed: update CONTENT set HIBERNATEVERSION=?, TITLE=?, LOWERTITLE=?, VERSION=?, CREATOR=?, CREATIONDATE=?, LASTMODIFIER=?, LASTMODDATE=?, VERSIONCOMMENT=?, PREVVER=?, CONTENT_STATUS=?, NAVIGATIONTYPE=?, PAGEID=?, DRAFTTYPE=?, SPACEID=?, CHILD_POSITION=?, PARENTID=?, MESSAGEID=? where CONTENTID=? and HIBERNATEVERSION=?], SQL: update CONTENT set HIBERNATEVERSION=?, TITLE=?, LOWERTITLE=?, VERSION=?, CREATOR=?, CREATIONDATE=?, LASTMODIFIER=?, LASTMODDATE=?, VERSIONCOMMENT=?, PREVVER=?, CONTENT_STATUS=?, NAVIGATIONTYPE=?, PAGEID=?, DRAFTTYPE=?, SPACEID=?, CHILD_POSITION=?, PARENTID=?, MESSAGEID=? where CONTENTID=? and HIBERNATEVERSION=? 

Workaround

Currently, there is no known reliable workaround for this behavior.

In some cases, hard-refreshing the browser (Ctrl+F5) may temporarily allow the Chart macro to render, but this is inconsistent and cannot be guaranteed. A workaround will be added here when available.