CMS Error: “You’re trying to modify an older version”

Written By Spandana Patnam (Administrator)

Updated at September 23rd, 2026

Authors may occasionally encounter an error while editing and submitting a story in the BOLD Workspace. The observed behaviour may include:

  • The CMS indicator at the top of the page turning red and then returning to blue.
  • The Submit button becoming unresponsive or failing to submit the story.
  • After reloading the page, some of the changes made during editing being lost.
  • The behaviour occurring intermittently, particularly when a story remains open for an extended period.

Why does this happen?

This behaviour can occur when the version of the story being edited is no longer the latest version available on the server.
Possible scenarios include:

  • The same story is being edited in multiple tabs or browsers.
  • Another user is editing or updating the same story at the same time.
  • The story is being accessed from another active session.
  • The story remains open for an extended period, causing the editor to work with an older version.
  • Temporary network interruptions result in the editor and server getting out of sync.
  • When multiple users or sessions update the same story, a version conflict can occur. This may result in an error when attempting to submit the changes.

Preventing concurrent editing

To help prevent version conflicts, the Block Concurrent Story Edit setting can be enabled.

When this setting is enabled, only one user can actively edit or update a story at a time. This helps prevent multiple users from making changes to different versions of the same story.

Concurrent Story Editing – Quintype Help Center


What to do when the error occurs

If the Submit button stops responding or an error appears:

  • Back up your changes before refreshing the page.
  • Check whether the same story is open in another tab or browser.
  • Confirm that another user is not editing the same story.
  • Refresh the story after ensuring your changes have been backed up.
  • Restore any changes that were not saved.
  • Submit the story again.

Important: Always back up your changes before refreshing the page, as unsaved changes may be lost.

To minimise version conflicts:

  • Avoid opening the same story in multiple tabs or browsers.
  • Avoid having multiple users edit the same story simultaneously.
  • Refresh stories that have remained open for a long period before continuing to make changes.
  • Ensure the internet connection is stable while editing and submitting stories.
  • Enable Block Concurrent Story Edit to prevent simultaneous editing of the same story.

If the behaviour continues

If the error continues after following the above steps, please share:

  • The affected story URL.
  • A screenshot or screen recording of the behaviour, if available.
  • The approximate time when it occurred.
  • The steps followed immediately before the error appeared.
  • This information will help with further investigation.