Skip to content
API, security & troubleshooting

Resolve save errors and conflicting edits

Preserve your work and distinguish validation, access and concurrent-edit failures.

CCorthex product guidesUpdated October 15, 20262 min read
Where to find itAny settings or editor form

Before you begin

Use a test environment and the smallest necessary access. Keep workspace API keys and signing secrets on your server, outside browser code and public screenshots.

Example workspace · Demo data. Start with the correct agent and review the save controls. Select the image to enlarge it.
Agent settings showing identity, prompt and conversation options

Example workspace · Demo data. Start with the correct agent and review the save controls. Select the image to enlarge it.

Step by step

  1. 1

    Read the displayed error

    Check whether the issue is a missing value, unavailable permission, network failure or another teammate’s newer edit.

  2. 2

    Preserve important text

    Copy an unsaved prompt or document to a safe internal location before navigating away. Do not include secrets in an external debugging tool.

  3. 3

    Fix the stated cause

    Correct invalid fields, restore connectivity or reload the latest server state when a conflict is reported.

  4. 4

    Reapply deliberately

    Compare your intended change with the latest state and save once. Verify the persisted result by reopening the screen.

Good to know

Repeatedly pressing Save can hide the cause and create competing changes. A visible preview is not proof the server accepted the change.

Check the result

Check the response, relevant delivery history and organisation scope. Use the Public REST API reference in this Help Center for the technical contract.

Questions & troubleshooting

I cannot save a setting I can view

Your role or plan may allow viewing but not editing. Check the workspace and displayed permission feedback.

Was this article helpful?

Rate this guide on this device. Ratings are not sent to Corthex.