HSX_E_LINK_MIGRATION_INTERRUPTED

Link migration was interrupted — resume by re-running.

What this error means

The journaled link migration crossed a step boundary and then stopped. The operation is journaled and resumable: re-running `hs-x link` picks up from the recorded boundary and converges without replacing any key or namespace.

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

Likely causes

The process was killed (or the injected-failure test seam fired) after a boundary was persisted
A transient failure between two step boundaries

How to fix it

Re-run hs-x link — it resumes from the migration journal and finishes the remaining steps idempotently

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