incidents
TS/Iwhat is an incident
An incident is any of the following: a position held by the batch, a transaction that reverted with one of the program's own error codes, a batch that opened but did not close inside its window, or a difference between this site and the chain. Incidents are not hidden. Each one gets a line here, and each one that required a decision gets a memo.
classification
| GRADE | MEANING | RESPONSE |
|---|---|---|
| Minor | A single position held, or a single reverted transaction with a named error. | Noted here. No memo unless a pattern appears. |
| Material | A batch that did not close in its window, or a rate sheet read that did not match a memo. | Memo within one working day. |
| Serious | Any difference between this site and the chain, or any transaction by the operator key not covered by a memo. | Memo the same day, and the batch does not run until resolved. |
the incident record
Each incident on this page has a grade, a source, and a status. The source is always the chain. The grade is assigned by the classification table. The status is one of: open, reviewed, closed by memo. A held position is open until the next batch settles it or a memo explains why it will not be. A reverted transaction is closed the moment it is listed, because there is nothing to do about it. An open batch is open until its closing memo appears.
what is not an incident
A counterparty's transaction that fails for a reason outside the program, such as an insufficient network fee or a wrong account, is not an incident. It never reached the program's code and the program has no record of it. A position that is held because its counterparty let collateral fall below ratio is a minor incident for the record and not a fault of the system. A rate change announced on time is not an incident, however unpopular.
review
Reviewing a held position means reading its collateral account, confirming the reason code is correct, and either doing nothing, because the counterparty has since locked more collateral and the next batch will settle it, or writing a memo, because the hold has persisted across more than one batch and somebody should say so. The desk does not contact counterparties. The memo is the contact.
a note on reason code one
Reason one, mint mismatch, should never occur, because open refuses a collateral account whose mint differs from the float's. If it is ever listed here, the only explanations are a defect in the program or a deployment whose interface differs from this page. Either is serious. The batch would not run again until a memo explained it.