Due to an errorneous assessment of VSN-2514 Scroll EditorServletFilter does not wrap a transaction around the invocation of the filter chain when processing page creation or editing. This is however done correctly with older Confluence versions.
The missing transaction context leads to partially constructed Scroll pages, whenever there is some condition that needs the transactional behaviour, for example duplicate page titles. This can also lead to duplicate changes for the same version for a single Scroll page.
We cannot be sure, but assume that this covers up errors for the user and depending on timing can also lead to corrupted Scroll pages without other errors being present. Since calls within the page post processing are not wrapped in a transaction you might encounter anomalies like phantom reads or deadlocks when the same thread acquires database locks in quick succession.