Skip to content

Saving Boss’nX schemas: troubleshooting and frequently asked questions

Boss’nXAdministratorInstaller

Boss’nX, schema editor of a supervision: loading, confirmation, layer summary and leaving

Empty editor, missing name, confirmation not found, bar at 100% despite failures, unsaved layers, server message or an old description coming back: here are the answers to saving problems in the schema editor of a Boss’nX supervision. The full procedure is in the name and save guide. For a schema block on the Dashboard and its Finish editing button, see its specific questions instead.

No. Viewing an existing schema requires no save: open Schemas in the header bar or in the Menu, then select its name and its layer. If you are in the editor with a draft, choose Stay to review it, or Leave without saving if you accept abandoning it. Only save the changes you want to apply.

Why is the editor empty although I opened an existing schema?

Section titled “Why is the editor empty although I opened an existing schema?”

First wait for the name and content to finish loading: a momentarily empty form does not mean that the schema has disappeared. Do not fill in the name or save to try to bring the drawing back.

If the editor stays empty:

  1. Return to Schemas, in the header bar or the Menu, and check the supervision.
  2. Clear any search.
  3. Open Actions → Edit schema on the right row and wait for loading.

If a leave prompt appears while you have prepared changes to keep, choose Stay before leaving. If the right schema stays empty or inaccessible, report it to support with its name and what you observed.

The message Please enter a schema name. appears when Schema name is empty or contains only spaces; the confirmation does not open. In the left panel, type a name, then click Save again. Description (optional) can stay empty.

If the Save schema? dialog opens, continue from this confirmation and judge the result of this new attempt: a message still visible from a previous attempt does not concern the next one. If the name is filled in and saving remains impossible, note the message and the step reached for support.

The first click only opens the Save schema? dialog. The Save button in this dialog starts saving; Cancel returns to the draft.

During Saving in progress, wait for the end without closing or refreshing the page. If sending remains stuck after you confirmed, or the expected result cannot be found, contact support with the schema name, the message and the steps tried. Do not conclude from this alone that data was lost.

Does a bar at 100% mean that all layers are saved?

Section titled “Does a bar at 100% mean that all layers are saved?”

Not necessarily. Read the summary, which counts saved layers and failures, then the state shown next to each layer: Queued, Sending, Saved or Failed.

Fictional example: 1/2 layers saved · 1 failure(s) can appear with 100%; one of the two layers is then not saved. Note the name of the failed layer and the displayed message, then try again. If that attempt also fails, contact support.

What if a message names layers that were not saved?

Section titled “What if a message names layers that were not saved?”

The message Failed to save layer(s):, followed by their names, states The other layers were saved. The result is partial: note the named layers, without assuming that everything failed or that everything succeeded.

If your changes are still in the editor, keep the page open, review them, then run Save and its confirmation again. If this new attempt fails, contact support with the layer names, the message and the attempts made. Leave without saving does not bring back the earlier version of layers already saved.

What if the server state cannot be verified?

Section titled “What if the server state cannot be verified?”

The message Could not verify server state. Please retry. reports that a check required for saving failed. Keep your draft in the editor, click Save again, then confirm.

If this new attempt fails, contact support with the schema and the message. This message concerns saving: do not change a device’s settings to solve it.

The message The schema id on the server no longer matches. Please reload the page. asks you to reload the page. A refresh can discard what is not saved: first check whether you have changes to keep.

  • If you accept losing them, reload the page, then reopen the right schema from the list.
  • If you need to keep a draft whose saving does not succeed, contact support before leaving the page.

Do not change the schema address to work around this message.

This button appears when the confirmation reports errors on the schema or on some elements. Read the messages and the named elements. Cancel takes you back to the editor to check them. Save anyway continues saving despite these messages, without guaranteeing that the elements can be used as intended.

If you do not have a reliable fix for the displayed error, contact support with the element, the layer and the message. Do not disable a function just to make the warning disappear. Red or orange badges, empty images and the decorative choice are covered in the questions about errors and warnings.

Save & leave waits for saving to succeed before leaving; while sending, the choices are disabled. If saving fails, the dialog may stay open so that you can stay, try again or leave without saving.

Note the message. Stay takes you back to the draft: check its name in particular, then run Save again. If the failure happens again, contact support. Choose Leave without saving only if you accept abandoning the changes still pending.

Check that you confirmed Save, or chose Save & leave, then reopened Actions → Edit schema on the right row and waited for loading. Cancel in the confirmation keeps the draft without saving it; Leave without saving abandons it.

To remove a description, clear Description (optional), then save. If the old description still comes back after these checks, contact support and describe the expected value and the one you found, without assuming the cause or concluding that nothing was saved.

Does Leave without saving cancel previous saves?

Section titled “Does Leave without saving cancel previous saves?”

No. This choice only abandons the changes still pending. It cancels neither a save already made nor the part of a partial result that was already saved. To change a saved value, reopen the right schema, prepare the value you want and save again, if you are allowed to.

What if Resolve conflicts or Resume appears?

Section titled “What if Resolve conflicts or Resume appears?”

Resolve conflicts indicates that changes were saved to this schema while you were editing. To choose the versions to keep, use Resume or understand a concurrent version, follow conflict troubleshooting.

Where are the answers about the canvas and datapoints?

Section titled “Where are the answers about the canvas and datapoints?”

If the problem persists after these checks, write to support@can-nx.com with: Boss’nX, the supervision, the schema name, the layers concerned, the exact message, the step reached and the attempts already made. A screenshot without sensitive data can help; no password or secret is needed.