In the context of an S2S
append or read session, an error that occurs after a 200 OK status will be a “terminal message” on the response stream. However, pre-flight errors are sent normally.Standard Errors
A standard error body has the following JSON form:Structured Errors
Append Condition Failed (412)
See concurrency control for more context.- Fencing Token Mismatch
- Sequence Number Mismatch
Read Range Not Satisfiable (416)
416 without a Range header? Unconventional, but the shoe fits.See when reads return 416.tail field indicates the current end position of the stream.
