Concurrent edits and save conflicts

Documentation / Saving, recovery, and troubleshooting

A conflict means the saved draft, live page, or review context changed after your editor loaded it. Beeboo uses revision checks to prevent a stale tab from silently overwriting newer work. Treat the conflict as a request to compare states, not as a reason to keep pressing Save.

Preserve and compare

Record the error and keep any unconfirmed text you need in an approved private location before reloading. Coordinate with the other editor and identify which tab or assistant last changed the page. Confirm the website, page ID, and content language; cloud drafts are shared for that specific target rather than isolated per browser tab.

Reload the canonical page and inspect the newer saved content. If cloud recovery exists, review it through Resume saved edits. Decide which changes to retain and reapply only the missing edits. Do not discard another person's saved draft without agreement.

Assistant and custom-design conflicts

An assistant should read the current page and retain pageModifiedAt, then include it as expectedPageModifiedAt on the approved update. Custom-design changes require that value. If it conflicts, read again and reconcile the proposal with the new page; replacing only the version token defeats the review.

Shared shells also check draft revision, activation version, and page/navigation/settings fingerprints. An unrelated dependency change can invalidate approval and require a fresh preview even when shell source looks unchanged.

Interrupted requests

A timeout does not prove that the server rejected the write. Read back the current state before retrying. If Finish publishing appears, it refers to a preserved publish snapshot and should not be mixed with a new edit.

For persistent failures, report timestamps, targets, versions, and redacted messages. Never include a token or private-preview secret. See agentic editing and connections and saving and recovery.