@@ -100,6 +100,15 @@ Since version `0.8.0`, changes no longer automatically sync between the Unix sid
101You may have booted a ship with your keyfile twice in the same era. To fix this, you must perform a [personal breach](#personal-breach).
101You may have booted a ship with your keyfile twice in the same era. To fix this, you must perform a [personal breach](#personal-breach).
103+### I don't have the latest OTA
105+You can check what build your ship is on by entering `+trouble` into dojo and
106+reading the `%base` hash. If this does not match the latest hash published in
107+the `urbit-dev` mailing list, you are behind.
109+Your sponsor may just be lagging behind, so sometimes this will resolve on its
110+own with patience. Otherwise, try the procedure outlined [here](https://github.com/urbit/support/wiki/Missing-OTA).
103### I keep getting an `ames` error stack-trace
112### I keep getting an `ames` error stack-trace
105You may see a message like this one: `/~zod/home/~2019.7.22..18.55.46..83a3/sys/vane/ames:<[line column].[line column]>`. This is a clay path to a Hoon file, pointing to the line and column where an expression crashed. This kind of error might be accompanied by a `crud` message.
114You may see a message like this one: `/~zod/home/~2019.7.22..18.55.46..83a3/sys/vane/ames:<[line column].[line column]>`. This is a clay path to a Hoon file, pointing to the line and column where an expression crashed. This kind of error might be accompanied by a `crud` message.