Hi everyone, I have been trying to get an answer f...
# orm-help
m
Hi everyone, I have been trying to get an answer for the past couple of days, but nobody has been responding 🤒 How does the prisma/yoga server handle hanging subscriptions? I have a local server instance runnning with a react native client attached. When I subscribe to a subscription, everything works fine. However, when I reload my app and subscribe again, the subscription updates are not received any more. How does prisma/yoga react, when the subscription websocket connection is simply broken, and a new one is established a few seconds later? is it possible that server side caching is causing this behavior? Thanks, I would really like to understand whats going on here, we switched back to polling because we cannot figure out how this behavior is caused. Would be glad about any feedback!
n
This sounds unexpected. I think your best bet to gain further insights is to provide a reproduction in a new issue at https://github.com/prismagraphql/graphql-yoga. Based on your description it is not entirely clear what is happening, and the possibilities are vast - so it's difficult to give you an answer to your question at the moment.
m
OK, thanks. Its already good to hear that this is unexpected behavior, I thought that maybe there was some kind of reconnection logic in place that I had to use. Documentation on subs is still rather thin. Ill look deeper into it. Btw, does prisma implement subscriptions with pubsub?
n

https://www.youtube.com/watch?v=wo9XFmW0W2câ–¾

🙂
this is a talk about our subscriptions architecture
m
🙌
n
you can use PubSub or any other mechanism in the GraphQL Server in front of Prisma.