You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository is currently being migrated. It's locked while the migration is in progress.
I'm using v2 WS API for orderbook syncing. I've stored each cancel from pushCancel and pushCancels messages using their ID as key in DB. But as i see, sometimes cancel is missed. For example, after cancel { "id": 38795396, ... } next is { "id": 38795398, ... } , but 38795397 is missed. I have tried to listen WS api parallel on 2 different machines, and both of them has same missed cancels.
The text was updated successfully, but these errors were encountered:
I'm using v2 WS API for orderbook syncing. I've stored each cancel from pushCancel and pushCancels messages using their ID as key in DB. But as i see, sometimes cancel is missed. For example, after cancel { "id": 38795396, ... } next is { "id": 38795398, ... } , but 38795397 is missed. I have tried to listen WS api parallel on 2 different machines, and both of them has same missed cancels.
The text was updated successfully, but these errors were encountered: