> For the complete documentation index, see [llms.txt](https://nytshift.gitbook.io/nytshift-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://nytshift.gitbook.io/nytshift-docs/arcus/arcus-reconciliation-incident.md).

# Reconciliation incident

Use this runbook when Arcus status reports `ARCUS_RECONCILIATION_INCIDENT_ACTIVE`, signer health reports one or more active reconciliation incidents, or an order reconciliation displays an automatic cancellation attempt.

1. Set and keep `ARCUS_EXECUTION_KILL_SWITCH=true`. Do not submit a new order and do not retry the original place or cancellation.
2. Keep the original signer database and `clientId`. Do not delete, replace, or edit `%USERPROFILE%\.nightshift\execution-idempotency.sqlite3` (or the configured signer database).
3. Run `pnpm signer:health`. Confirm `automaticCancelPolicy=required`, `reconciliationSafe=false`, and a non-zero aggregate incident count. The health response deliberately does not disclose order identities.
4. In the authenticated terminal, use **RECONCILE CLIENT ID** for the affected order. This calls the signer-owned public lifecycle reconciliation. If that read fails, the signer may make the one pre-authorized cancel-by-client-ID attempt. It never retries that attempt.
5. Interpret the result conservatively:
   * `FILLED`, `CANCELED`, or `REJECTED`: the signer resolves that incident.
   * `OPEN` or `PARTIALLY_FILLED` after an automatic attempt: the incident remains active; do not retry.
   * automatic cancellation `acknowledged`: queued only, not complete; reconcile again later.
   * automatic cancellation `rejected`, `unknown`, or `pending`: the incident remains active; do not retry.
6. If exposure must be reduced across the whole configured account, use the separately reviewed **Review cancel all** control while the kill switch is active. Its ACK is also non-final; keep reconciling until the live open-order count is zero.
7. Keep ordinary entry locked until the affected client ID itself reaches a terminal lifecycle state and signer health returns `reconciliationSafe=true` with zero active incidents.

If public lifecycle reads remain unavailable, preserve the latch and signer state. Provider recovery, Arcus support, or independent account evidence may be needed, but lack of local process state is never proof that an order failed.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://nytshift.gitbook.io/nytshift-docs/arcus/arcus-reconciliation-incident.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.