OneEnv

Troubleshooting

Error codes taken from the backend, with what to do.

By the OneEnv team · Last updated

These are the codes and messages the backend actually returns.

Code or symptomCauseFix
MERGE_CONFLICTSomething changed an item after your branch began (or last rebased).Open the branch, choose Rebase, re-check the diff, submit again.
BRANCH_NOT_DRAFTYou tried to stage, submit or discard on a branch that is already submitted, merged or rejected.Create a new branch.
BRANCH_NOT_SUBMITTEDA merge was attempted on a branch that is not submitted.Submit it first; if already merged, nothing to do.
BRANCH_NOT_MERGEDRevert is only for merged branches.Pick a merged branch.
No staged changesSubmitting an empty branch.Stage at least one edit.
DUPLICATE_KEY (409)Name or key already exists, archived items included.Choose a different name.
ALREADY_MEMBER (409)The invited email is already active or invited.Change their role instead.
CANNOT_EDIT_SELF / CANNOT_EDIT_OWNERRole dropdown limits.Ask another admin; use transfer ownership for Owner.
LAST_OWNERRemoving the only active Owner.Transfer ownership first.
SERVICE_ACCESS_DENIEDNo view permission on that service.Ask an Owner or Admin for a grant.

Symptoms without a code

  • Edit forms disabled: select or create a branch in the top bar.
  • Invited person cannot see the workspace: they must log in with the invited email address (no email is sent).
  • A service's export did not change after merge: that service has not approved its impact.
  • A member cannot see a service: grant view or higher, or a default grant.
  • Local development: the login code prints in the backend log ([dev-only] OTP for ...).