drift doctor
The one place to go when something is wrong. Everything here runs offline and without a session, because that's when you need it.
| Command | Description |
|---|---|
drift doctor explain <code> | Expand a DRIFT-#### code into what happened and what to do |
drift doctor codes | List every failure code this binary can produce |
Every failure the CLI prints carries a code. explain takes it with or without the DRIFT- prefix, drift doctor explain 1006 and drift doctor explain DRIFT-1006 are the same lookup, and prints the meaning, the remedy, and, where one exists, the exact command that fixes it, held to three words or fewer. Where there's no command that helps, a platform fault or an unreachable network, it says so rather than sending you somewhere that fails again. It ends with the address of that code's section on this page, printed and never fetched, so it works offline too. A code explain does not recognize prints no address.
$ drift doctor explain DRIFT-1003
DRIFT-1003
The thing you named does not exist on the platform.
Check the spelling, and that your active slice is the one you mean —
`drift slice list` shows what the account actually has.
fix: drift slice listThe registry is compiled into the binary, so doctor answers during an outage: no network, no login, which is exactly the condition you're in when you're holding a code in the first place. drift doctor codes lists all of them at once, useful when you have the symptom but not the code. A Driftfile that is invalid, or a compiled Function that books less than its language needs, has its own codes (drift doctor explain 1009, drift doctor explain 1010), and the fix for the second is drift size.
A retired code still explains.