--- title: "Boss’nX schema conflicts: troubleshooting and frequently asked questions" description: "Server version checked, window gone after Switch to layer, zero counters, conflict not resolved: answers about layer conflicts in Boss’nX schemas." canonical: https://wiki.can-nx.com/en/guides/boss-schema-conflicts-help/ language: en product: Boss’nX audience: - administrateur - installateur context: "Boss’nX, schema editor on a computer: Resolve conflicts window and save" --- # Boss’nX schema conflicts: troubleshooting and frequently asked questions Context: Boss’nX, schema editor on a computer: Resolve conflicts window and save Unexpected **Resolve conflicts** window, server version already checked, window gone after **Switch to layer**, counters at zero, conflict not resolved or wrong version confirmed: here are the answers to common questions about layer conflicts in the schema editor of a Boss’nX supervision. The full procedure is in [choosing the versions of layers](https://wiki.can-nx.com/en/guides/boss-schema-conflicts/). For a partial save or a server check that cannot be done, also follow [general editor troubleshooting](https://wiki.can-nx.com/en/guides/boss-schema-editor-help/). ## Why does the Resolve conflicts window appear? Changes were saved to this schema while you were editing. The window asks which version to keep for the layers concerned. Read the name of each layer, the **Server** and **You** information, then the proposed versions. This message is about the layers shown: it does not indicate that the whole schema is lost or that all your changes failed. ## Is the checked server version already applied? No. The check mark shows the choice prepared for this layer. **Keep server** is preselected when the window opens, and nothing is saved before **Save with choices**. Check all the cards before starting this save. If you do not want to continue, click **Cancel save**. ## Can I keep my layer name and the background changed by the other person? Not in this window. Its choices apply to a complete version of each layer, without an automatic property-by-property merge. You can choose differently from one layer to another, but **Keep mine** keeps your version of the layer: changes present only in the other version of the same layer may be replaced. If you do not know which version to keep, click **Cancel save** to review the draft. Have the differences reviewed before replacing work that must be kept. If the decision remains uncertain, contact support with the schema, the layer and your goal. ## Does Yes, keep mine for all save my choices? No. The **Yes, keep mine for all** confirmation prepares the global selection. Return to the cards, check the selected choices, then click **Save with choices** if you want to apply them. After the save, check the message, the summary and the result in the right layer. ## Why is there no confirmation with a single conflict? **Keep all mine** directly selects your version when there is only one conflict. With several conflicts, an extra confirmation, **Overwrite other users' edits?**, asks whether you want to prepare the replacement of other users’ changes. In both cases, the save happens with **Save with choices**. ## Where did the window go after Switch to layer? It is collapsed into a **Resume — … conflict(s) pending** button, at the bottom right. The choice of versions is still pending while you view the layer, which is why **Saving…** is still displayed. Click Resume, or press Esc to reopen the collapsed window, then save with your choices or cancel the save. **Switch to layer** shows the layer in the editor, not necessarily the server version. If Resume remains out of reach on your screen, try a wider screen. If you still cannot resume the decision, contact support, keeping the page open if possible. ## What do baseline unavailable and author unknown mean? **baseline unavailable — showing current state only** means that the detailed comparison is not available. **(author unknown)** means that the author’s identity is not shown in this summary. In both cases, do not conclude that there are no changes or who made them. If this information does not let you choose reliably, click **Cancel save** and contact support, specifying the schema and layer names, the message and the changes you want to keep. ## Why are the counters at zero when a background or name change is shown? The **Added**, **Modified** and **Removed** lines count the elements concerned. Changes to the layer itself can appear separately, in particular **layer name changed**, **background changed** or **canvas size changed**. Two different versions can therefore show counters at zero: also read the lines below the counters. ## What do layers applied automatically mean? A note at the bottom of the window, or a message after the save, can indicate that layers modified during your editing were applied automatically. These are layers modified on the server with no local change on your side: their changes are taken over. The server version is not imposed on your conflicting layers for all that; they follow the choices made in the window. Check the schema and the layer concerned. If the result still does not match what you expected after review, contact support with the message and what you observed, without inferring a global loss from this message alone. ## Why does Keep the server version appear for a layer I deleted? Someone else modified this layer after you loaded it. **Keep the server version** abandons your local deletion for this layer when saving; **Delete anyway** prepares its deletion despite the other change. Choose according to what you want to keep, then click **Save with choices**. Clicking an option alone saves nothing: check the layer list after the save. ## What if the conflict could not be resolved? The message **The conflict could not be resolved — try saving again.** indicates that the save with your choices did not succeed. Keep your draft in the editor. Run **Save** again, then its confirmation, and review the choices if the conflicts reappear. Check the result after the attempt. Do not systematically choose **Keep all mine** to make the message disappear. If you have already retried without success, contact support. ## What if I chose the wrong version and confirmed the save? First check the result in the right schema and the right layer: this check tells you what was actually saved. **Cancel save** concerns the decision in progress; it does not restore a save that has already completed. If the expected result cannot be found and you do not have a reliable procedure to restore it, contact support. Describe the version chosen, the confirmation made and the result actually observed, without concluding that recovery is guaranteed or that everything is lost before you have observed it. ## Contact support If the problem persists after these checks, write to support@can-nx.com with: Boss’nX, the supervision, the schema and the layers concerned, the exact message, the version chosen and the result observed, the changes you want to keep and the steps already taken. A screenshot without sensitive data can help. Do not send any password, token or confidential access link.