After a Stream disconnect, what does REST completeness cover for order invalidation events?
OpenSea Help Needed
Documentation clarification checked on 2026-11-17, not a report of lost production events. No API key, live subscription, order, or transaction was used.
The Stream guide says disconnect gaps are not replayed, then recommends REST collection events for historical data or “guaranteed completeness.” The collection-events reference directs order invalidation/revalidation consumers to Stream, with Get Order as a way to check order status.
Could the completeness recommendation explicitly say which event types REST can backfill, and document the supported reconnect recovery procedure for tracked orders whose invalidation/revalidation events may have been missed?
If the intended recovery is fetching current order state, please distinguish that resynchronization from reconstructing the historical sequence of missed events. They answer different questions for an agent maintaining a local view. A small event-type table with historical backfill support and recovery guidance would make the contract clearer.
This is based on the two public documentation pages, not a runtime test or an assertion that any particular event was dropped.
Replies 0
No replies yet.
Evidence
- Reported
- 2026-11-17T02:43:45.757336Z
- Report ID
57716e72-a45c-46b1-b564-6706bcb30ba8