Whole-request refusals and per-change outcomes in the words the clients show, what each means, what to do, and in what order the server checks them.
A refusal is never silent. It comes either as a whole-request answer (nothing in the batch was attempted) or as a per-change outcome (this change was refused, the others may have been applied). The browser lists refused changes under the map with their reason; Hyz Desktop shows them as conflict rows in the sync dialog; a Field record keeps the reason on the record. The words below are the ones the clients show.
| You see | Meaning | What to do |
|---|---|---|
| the Editing panel is missing, or editing is not enabled | this instance does not have editing switched on | an administrator sets it in the API configuration |
| editing is switched off for this layer | the owner has not switched it on for this layer | ask a manager of the item; managers see the switch on the item |
| you do not have permission | your role on the item, or in the organization, does not carry this operation | ask the owner for the editor role, or a manager for what you need |
| access to this data item is denied for you | a deny was placed on the item for you or a group you are in | only the owner can remove a deny |
| the data item belongs to another organization | your organization role does not reach this item | ask for a direct grant on the item |
| Your plan's limit of editable layers is reached. | the owner's plan allows no more editable layers | switch editing off elsewhere, or see limits |
| the plan's edits per month are used up | the owner's monthly edits allowance is spent | wait for the month to turn or upgrade; nothing already applied is lost |
| a layer is being edited; snapshot or disable first | you tried to upload a new file version onto an editable item | take a snapshot or switch editing off, then upload |
| Your copy is older than the portal's change log … | your Hyz Desktop checkout is below the layer's log floor, or the layer was restored | check the layer out again; copy your edits across |
| the layer is not ready | the Hyz Layer is still importing, needs a mapping, or failed | wait, supply the mapping, or fix the file |
| You see | Meaning | What to do |
|---|---|---|
| this operation is switched off for the layer | the rules do not allow create, edit or delete | a manager widens the allowed operations |
| you do not have permission | you may do other operations on this layer but not this one | ask for the role that carries it |
| the feature is locked | the feature's lock flag is set | a manager unlocks it, one by one or by filter |
| the feature no longer exists | someone deleted it after you loaded it | reload; re-create it if it should exist |
| deleted on the server | (Hyz Desktop) you changed a feature the portal has since deleted | choose Portal to accept the deletion, or re-create it as a new feature |
| only its creator may change it | the rule Editors change only their own features is on and you are not its creator | ask a manager, who is exempt, or the creator |
| geometry is not editable on the layer | you moved or redrew a shape on a layer whose geometry is read-only | change attributes only, or ask a manager to allow geometry |
| this field is not editable on the layer | the field is excluded from the editable fields | edit the other fields; ask a manager to include it |
| outside the editing area | the feature, or where you moved it, lies outside the layer's editing area | move it inside, or ask a manager to widen or remove the area |
| a required field is empty | a new feature lacks a value for a required field | fill it and save again |
| a new feature needs a geometry | a create arrived without a shape | draw the feature before saving |
| invalid geometry | coordinates are not finite numbers, or the shape cannot be built | redraw; in Hyz Desktop run Make valid first |
| the geometry type does not match the layer | a line on a point layer, a polygon on a line layer | draw the layer's type; a different shape belongs in a different layer |
| the value does not fit the field | text in a number field, a date that is not a date, a field that does not exist | correct the value; check the field list on the layer |
| changed on the server since you loaded it | a conflict: someone changed the feature after you read it, and the policy is reject the later one | reload and re-apply; in Hyz Desktop choose Mine to overwrite or Portal to take theirs |
| unknown operation | a client sent something the server does not understand | update the client; report it if it persists |
Outcomes marked as duplicates are replays of a change the server already holds; they report what happened the first time and change nothing. That is expected after a retried sync.
The server stops at the first "no", so one refusal can hide another. When a change is refused for the feature is locked, unlocking it may reveal outside the editing area. The order is: editing on, operation allowed, permission, fields, geometry well formed, then, for an existing feature: exists, locked, own, geometry read-only, conflict, and last the database checks (values, geometry type, editing area). The rules explains each.
Administrators have the same view with reasons in the Console's effective-access explanation, and the operator runbook maps every code to its cause.