Errors

A refused call is a tool error whose structuredContent holds Sherpo's code and its context.

• not_found: nothing matches the reference given.
• not_entitled: the resource is held back from this connection.
• not_permitted: this connection may not make this call. A revoked or expired connection answers HTTP 401, a missing scope HTTP 403 insufficient_scope.
• not_permitted with limit in its context: too many calls; retry_after says when to try again where it is known. Each store counts a connection's calls on its own.
• conflict: the call clashes with the current state.
• invalid: an argument is malformed; context.path names it.
• internal and unavailable: the call failed inside Sherpo. A read marked transient may be retried; after a failed write, read the state back before trying again, since a write carries no idempotency key.
• client-fault: this server failed around the call. reached_core says whether it reached Sherpo, and core_answer what Sherpo answered: ok means a write landed.