SILOC error list

Look up SILOC error codes, the HTTP status each one carries, and the action that resolves it.

Error format

SILOC returns errors as RFC 9457 problem details:

JSON

{
  "type": "https://errors.lerian.studio/v1/SILOC-0007",
  "title": "Not Found",
  "status": 404,
  "detail": "participant not found",
  "code": "SILOC-0007"
}

Field definitions

• type – A URI that identifies the error in the Lerian error catalog, built as https://errors.lerian.studio/v1/<code>. This URI repeats code, so it does not separate two statuses that share one code.
• title – The HTTP status text (for example, Not Found).
• status – The HTTP status code.
• detail – A human-readable explanation for this occurrence. A 500 and a SILOC-0023 replace the text with internal error, so the internal cause stays inside the rail. The text varies per occurrence, and a 403 can carry the message the authorization service reported. Do not branch on it.
• code – The stable, machine-readable code (SILOC-NNNN). Dispatch on the pair of status and code, not on code alone. One code can appear under more than one status, and each status needs a different action. For example, SILOC-0022 is a 400 for a body that is not valid JSON and a 422 for a value that breaks a domain rule. A request that fails schema validation carries SILOC-0022, and errors names the fields at fault.
• errors – An optional list of field-level details, each with the location it read, a message, and the value found there. A refusal from the authorization or idempotency gate carries an empty violations list instead.

The tables below list the codes SILOC returns, grouped by HTTP status.

​

400, 413, 415: Request body refused

---

Status	code	Description	detail
400	SILOC-0022	The request body is missing, or it is not valid JSON. Send a JSON body that matches the schema of the operation.	request body is required, validation failed
413	SILOC-0022	The request body reached the 1 MiB limit. Send a smaller body.	request body is too large limit=1048576 bytes
415	SILOC-0022	The request declares a Content-Type that is not JSON. Send the body as application/json.	validation failed

​

401: Unidentified caller

---

code	Description	detail
SILOC-0004	The request arrived without a bearer token, or with a credential the authorization service does not accept.	Missing Token, or Unauthorized
SILOC-0003	A state-changing request reached the idempotency gate without an identified caller to attribute the X-Idempotency to.	authenticated principal unavailable
SILOC-0401	A certificate operation reached the rail without a caller identity to record.	authorized actor identity is unavailable

​

403: Refused caller

---

code	Description	detail
LCS-NNNN	The Lerian license refuses the request. Check the license in LICENSE_KEY or LICENSE_FILE_PATH.	None. The body carries code, title, and message.
SILOC-0005	The authorization service refused this caller for the resource and action the request targets, or, on a close approval, the caller is the operator who asked for the close.	Forbidden, the message the authorization service reported, or the operator who asked to close this message cannot approve it

​

404: Not found

---

code	Description	detail
SILOC-0007	The path or query named a resource the rail does not hold. Verify the identifier, or list the collection to find a valid one.	participant not found, certificate not found, alert not found, relay failure not found, quarantined frame not found, cycle not found, settlement instruction not found, multilateral result not found, no outbound instruction with that id, homologation scenario not found, business calendar year not covered, no card message with that id, no card command with that id

​

409: Conflicts

---

code	Description	detail
SILOC-0009	The request collides with state the rail already holds, or with a command that already spent this X-Idempotency. Re-read the current state before you retry. This includes a certificate whose authority and serial are already registered, and a close request for an outbound request that is not held, that already awaits its approval, whose parked answer can still replay, or whose LBTR cycle a later recorded close keeps open.	a participant with this ISPB already exists, the active credential cannot be disabled; revocation was not recorded, alert is already inactive, notification config was modified concurrently; re-read and retry with the current version, a run is already in progress for this scenario; wait for it to finish, a request with this idempotency key is still being processed; retry once it completes, the idempotency key was already used with a different request, an earlier request with this idempotency key ran and its answer cannot be replayed; reconcile the original request, and never retry it with a new key
SILOC-0026	An LTR0002 or LTR0008 names an operation whose earlier answer is SUBMITTED, DISPATCHED, or ANSWERED. The rail stored nothing. An earlier answer that ended FAILED or REFUSED reopens the operation, and an answered LTR0002 or LTR0008 confirmation (C) still takes a D answer for the same operation.	an answer to this operation is already live: a new one is accepted only after it failed or was refused

​

422: Validation errors

---

code	Description	detail
SILOC-0022	The request is well formed but breaks a domain rule, or carries a value the rail cannot read. Correct the field the response names and send the request again.	validation failed, X-Idempotency header is required on a state-changing request, X-Idempotency must be at most 255 characters, invalid pagination cursor, participantId must be a valid uuid, certificateId must be a valid uuid, id must be a valid uuid, authorized actor identity is unavailable, from/to must be an RFC 3339 date-time, decidedAt must be an RFC 3339 timestamp, movementDate must be a date in YYYY-MM-DD form, id must be a uuid, movementDate later than today in Brasília on an LTR0002 or LTR0008, an invalid field on a close request, invalid command: <date> is not a business day, so its LBTR cycle is closed all day on a windowSeq 3 schedule change, or the rule a card command breaks
SILOC-0025	An LTR0002 or LTR0008 decision arrived outside the LBTR cycle of its movementDate: after 17h30 Brasília or the later close an operator recorded for that day, or on a day that is not a business day. Any other outbound request names a DtMovto whose day already ended in Brasília. Only a query may name a past day. The rail stored nothing.	the LBTR cycle of the movementDate is closed: it runs 06h40 to 17h30 Brasília, or to the later close an operator recorded for that day, on business days only, and the câmara takes no LBTR decision outside it, or the movement day of DtMovto has ended in Brasília: a request leaves only on the day it claims, and only a query may name a past day

​

500: Server errors

---

code	Description	detail
SILOC-0500	An unexpected server fault. The rail masks the cause and returns a fixed text. Retry the request, and quote the trace identifier of the response if the fault persists.	internal error

​

503: Rail cannot answer

---

code	Description	detail
SILOC-0001	The rail could not reach a decision about this caller. The authorization service did not answer, or the deployment cannot authorize with its current configuration.	Service Unavailable
SILOC-0002	The idempotency store failed before the command ran, so the command did not run. Retry with the same X-Idempotency.	the idempotency store is unavailable, so this command did not run; retry it with the same key
SILOC-0023	This deployment has no send leg to Núclea, so it cannot send the requested message.	internal error
SILOC-0024	The send leg to Núclea is not running on this deployment, Núclea’s SILOC queue manager cannot be reached, or the signing certificate or the câmara certificate cannot be used: it is not registered, revoked or out of validity, the custody cannot sign with it, or the custody key does not match it. The rail stored nothing. Retry with the same X-Idempotency once it recovers. When the queue manager refuses this deployment’s own configuration, detail names the setting to fix.	internal error, Núclea is unavailable: the SILOC queue manager cannot be reached, so the message was not stored; retry once it recovers, or the setting the queue manager refused, followed by the message was not stored, retry once it is fixed

A 503 that carries SILOC-0002 means the command did not run. Retry with the same X-Idempotency. When only the receipt of a command that ran is lost, the rail returns the command’s own answer with the X-Idempotency-Fenced header. When the answer of an earlier request cannot be replayed, the rail answers 409 SILOC-0009. Reconcile the original request, and never retry it under a new key.