> 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/market-data-and-providers/feed-stale.md).

# Market or account feed stale

1. Freeze all new-entry intents; retain reduce-only mode only if the required account and price state remains inside its stricter freshness policy.
2. Mark affected symbols/accounts stale in the API and UI.
3. Stop the old socket, reconnect with jitter, resubscribe and process the snapshot acknowledgement.
4. Query Info for metadata, account state, open orders and fills since the last durable cursor.
5. Rebuild materialized state idempotently and compare invariants.
6. Resume only after freshness and divergence metrics remain healthy for the configured stabilization window.
7. Preserve trace IDs, timestamps, gap duration and recovery actions in the incident record.

## Robinhood Chain oracle context

1. Confirm the API state is `stale` with `ORACLE_HEARTBEAT_EXCEEDED`; do not substitute a market-data API or the previous numeric answer.
2. Compare `observedAtMs`, `upstreamUpdatedAtMs`, the reviewed heartbeat, registry version and canonical token/feed addresses.
3. Check sequencer uptime and token `oraclePaused()` before treating the incident as feed-only.
4. Compare primary and fallback providers at the same reviewed configuration. Any provider divergence keeps the value unavailable.
5. Resume display only after a positive, complete round is heartbeat-fresh and all sequencer/pause controls pass. No manual UI override exists.


---

# 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/market-data-and-providers/feed-stale.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.