Moreover, now I reverted permissions back, and it still doesn’t work. It might be related to a similar issue I've noticed: when I change my schema with new fields and use them right away in a subscription, it throws that these fields are not available on the schema, and only after some time this error goes away

@barbatus hey, thanks for this issue. We're aware of it and are already working on a fix 🙂 Right now schema changes take some time to affect your subscription schema

@nilan We are also experiencing issues with mutation callbacks. During testing on our staging we noticed that microservices are not called from time to time while appropriate DB entires have been successfully modified or updated (due to absence of logging from these microservices, they are running in the Now cloud). What could it be: a bug on your side, an issue with the microservices infrastructure or some other thing along the way from your side to the cloud?

hey @barbatus have you managed to pinpoint this issue, or even reproduce it? I'm not aware of a similar report, so any information on reproducing that would be super helpful!

@nilan we are still facing this issue with the subscriptions that are not aware about new fields or permissions update. It's been for a while since I reverted permissions to the default state and even recreated new same ones (everyone can edit, view, create) but it didn't help. Any advices how to fix it? maybe some workaround exists...

we're already working on a fix for the subscription schema not being updated, you can track the progress here: https://github.com/graphcool/api-bugs/issues/38