error_code

What went wrong with a request, as the JSON-RPC error's code (its number) and message. Every error's data also says how to recover (a recover value) and, unless that is none, the one next action to take.

Value	Meaning
`parse_error`	The request line is not JSON, or not UTF-8 text. Send one JSON object per line.
`invalid_request`	The line is JSON but not a JSON-RPC 2.0 request: it lacks `jsonrpc`, `method`, or `id`, or is longer than the daemon reads.
`method_not_found`	No operation has this name. The `op` vocabulary lists every operation.
`invalid_params`	The operation exists, but its `params` don't fit it: a field is missing, has the wrong type, or is out of range.
`internal_error`	The daemon failed to finish the request. A transient fault (a part of the daemon not yet running, a document that failed to load) clears on a retry; a daemon bug does not.
`no_participant`	The connection has not said which participant it acts for: the first request on a connection must be `hello`, with a participant this daemon knows and the connecting OS user may act as.
`unknown_base`	The request is based on a version of the document this daemon doesn't have. Read the document again and redo the change from what it holds now.
`out_of_bounds`	A change reaches past the end of the document at the version it is based on. Read the document again and redo the change from what it holds now.
`rejected`	A rule refused the request: the error's `rule` names which one, and its recovery is that rule's.
`rate_limited`	The participant sent requests faster than its rate allows. Wait the time the error gives, then send the same request again.
`secret_detected`	The change looks like it holds a secret (a key, a token, a password), so it was held and not shared. Confirm it holds none, or change the request so it doesn't.
`path_collision`	The path collides with another one that differs only by letter case or Unicode normalization, or names an existing directory. Choose another path.

Cardinality: 12.