Graphql subscription is not reliable

[kkoechley]

I think the best way to ensure you get the subscription events is the cursor.

If you miss an event, you should be able to get all the events from a given point in time. But the problem is that you need the events fired in a particular order, and they are returned in a different order? Or are the slow/missing events not returned at all when using the cursor?

@Amerehei

One more question, as the events are sequential, When I face a lost event (it seems the event is very very slow to get) I lost the sub-sequential events as well. I need to get the first event before I get the second. So when the first event is slow to receive (or lost) the second one is blocking

Is there any mechanism to detect this problem and is there any workaround to it?