Closed stefanoTron closed 6 years ago
Thanks. Can you prepare a minimal setup for which you confirmed this to happen?
1) In the console create a type like this:
type Post @model {
id: ID! @isUnique
title: String!
}
2) Manually, in the console, create two Posts
, with as title
Title1
and Title2
3) Then in the playground enter this and then execute:
subscription updatePost {
Post(
filter: {
mutation_in: [UPDATED]
}
) {
mutation
node {
title
}
}
}
4) Now go and change Title1
to foo
5) Observe in the playground if anything happened. Sometimes it does, sometime it doesn't, you might have to change the title
multiple times before the issue occurs or/and stop and start the subscription. In that case you have to repeat step 4, but instead of foo
another value like foo2
and so forth.
Same thing happening here.
@marktani @dpetrick @nikolasburk @schickling this issue is still happening, is there anything we can do to help?
I'm investigating the issue and I'll try a few fixes over the next hour.
Fixed, closing this issue. Reopen if it happens again.
thanks, let's hope it does not
Current behavior Sometimes subscriptions work, sometimes they don't. There is no precise pattern. Our code has not changed in weeks, nor have our dependencies.
Reproduction Setup real-time subscriptions with Apollo (I'm using
apollo-client 2.3.2
), or use the Playground. Observe how sometimes nothing happens on a CREATE or a UPDATE mutation.Expected behavior? When creating/updating a subscribed node, it should trigger a CREATE or UPDATE mutation, everytime in realtime.
Thanks