Skip to content

Graphql-ws Client not reconnecting after failed connection #357

Answered by enisdenjo
Ryiski asked this question in Q&A
Discussion options

You must be logged in to vote

Similar to #355.

All non-close-event connection problems are considered fatal by default. Your client seems to be throwing an Event, which is not a WebSocket CloseEvent.

If you want the client to retry regardless, you can implement your own shouldRetry option and have it return true always (or with pre v5.8.0 the now deprecated isFatalConnectionProblem option and return false always).

Replies: 1 comment 5 replies

Comment options

You must be logged in to vote
5 replies
@Ryiski
Comment options

@enisdenjo
Comment options

@Ryiski
Comment options

@enisdenjo
Comment options

@Ryiski
Comment options

Answer selected by Ryiski
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
2 participants
Converted from issue

This discussion was converted from issue #356 on April 25, 2022 10:36.