Troubleshooting | Whalehunt | Polymarket Realtime Data

Start with the symptom and preserve the local checkpoint.

Symptom	Check	Safe response
No hello	WSS endpoint, TLS and close symptom	Keep certificate validation enabled
No subscribed	Auth/subscribe deadlines, scopes/filter, error	V1 has no authenticated frame
Subscribed but no trades	AND predicates, frozen mapping, quality, checkpoints	Quiet-wallet progress is valid; inspect source health
Gaps in ordinals/positions	Filter selection	Original ordinals need not be contiguous
Gap in frameSequence	Integrity of this connection’s processing	Stop applying through an unknown gap
Duplicates after reconnect	Dedup IDs and durable token	Do not add duplicate volume
ACK rejected	Connection, generation, token, local commit	Fence stale handlers
Resume rejected	Code, floor, history and binding	Resolve reset explicitly
Slow consumer	Commit time, queue bytes/age, external work	Bound staging and improve processing

Safe operator diagnostics

Use the protected channel arranged for your integration. Include UTC time, code/retryable, connection/stream/history IDs, consumer/subscription IDs, generation/filter hash, last contiguous frame sequence, committed checkpoint position without its token, floor/cut, delivery health, transport symptom and client version.

Exclude API keys/tickets, full cursor tokens, signed orders/transactions, raw payloads, provider credentials, database connection strings and TLS private keys. Do not automatically publish identifiers in an open issue.

Conflicting event contents, unexplained history changes, unknown correction targets and unrecoverable local state require explicit investigation. Do not report successful recovery while hiding these problems.

Use the agreed operator channel; this interface does not establish a public support URL or response SLA. See errors and recovery.