HSX_E_LINK_PREFLIGHT_AMBIGUOUS

Link preflight: install bindings are ambiguous.

What this error means

Two runtime bindings claim the same INSTALL_KV namespace or the same token-key custody entry, so the continuity plan cannot uniquely attribute the resource. Link made no changes.

When this error stops a command, hs-x exits with code 10. With --json, the failure is reported as a structured error whose code field is HSX_E_LINK_PREFLIGHT_AMBIGUOUS — stable to match on in scripts and agents.

Likely causes

Binding records copied between environments or apps by hand
An older CLI bug that reused a namespace across environments

How to fix it

Inspect the two binding keys named in the error and delete or fix the stale one
Re-deploy the affected app/environment (hs-x deploy) so it provisions its own namespace, then re-run hs-x link

Still stuck? Re-run the command with --debug for the wire-level detail, or hs-x doctor to check accounts, link state, and connectivity in one pass.

Keep going