Resolve conflicts due to multiple users
When multiple users edit the same source, if one user publishes their draft, the next user attempting to publish will encounter an error due to a conflict. The error is usually something like Connector Content has been changed in version: x.
To avoid conflicts when publishing a source, we recommend
-
Staying in sync with the rest of your team when modifying sources.
-
Optionally, if you've made complex changes like adding JavaScript code, save the code on your local system. Then, if you lose your changes because of conflicts, you can refer to your local copy.
Conflicts arise because internally, Search differentiates between the published version of a source and the draft version of a source. If published source has version X, a draft source cannot also be in version X.
Consider this scenario: a source is published and in version 3. Users A and B edit this source at the same time. Now, for both A and B, the source is in the draft state and in version 4 (an increment of 1 from version 3). A publishes the source. The following things happen:
-
The source is published and in version 4.
-
For B, the source is still in the draft version 4. This causes a conflict because there is a published source in version 4 and a draft source in version 4.
-
To handle this conflict, B reverts the source to the latest published version. Now, B has the published version 4.
-
Optionally, if B edits the source, the source moves to draft state and is incremented to version 5. If B publishes their changes, the source moves to the published state and is in version 5.
If you publish a source and get an error message saying that there's a conflict.
To resolve conflicts due to multiple users:
