DA Live section moves can leave the next block in the old place

A page can look reordered in an editor while subsequent edits still use the previous document position. A DA Universal issue reproduces a section move followed by a block addition that appears in the old section location. A newer DA Live issue tracks related ordering work. Both are issue reports, not proof that every authoring environment is affected.

Reproduce with a disposable page

In a staging page with two clearly named sections, move one section and save. Add one uniquely named block immediately afterward, save again, and compare the editor tree, source document order and rendered page. Repeat after a reload. Record the editor build and whether the block was added through the insert control or copy/paste; those details help isolate the path.

Set an authoring release check

For pages with many sections, require a structural readback after moves before authors continue adding components. Adobe’s Universal Editor guidance documents moving components and undo/redo, but the acceptance test is the persisted page order. A visual preview alone may miss where a block will attach on the next edit.

Escalate without losing intent

If the order diverges, capture the before and after document versions and a short screen recording. Restore a known-good version only after preserving the disputed revision, then rebuild the change in small steps. Give support the issue link and reproduction. Avoid bulk rearrangements on a launch page until the exact editor version passes the test.

Adovo’s view

An editor is trustworthy when the next edit lands where the last edit said it would. Content teams need a persisted-structure check after a move, especially before campaign pages accumulate more blocks. A clean canvas is not enough evidence of a clean document.