We are spontaneously hitting this error on custom graphql resolvers: “FunctionError: read preference in a transaction must be primary”.
These resolvers don’t have any transactions inside them, just plain
We’ve been getting these errors since at least 21st of May.
Realm’s support acknowledged the problem, but it wasn’t able to give us any estimates of when this issue might be fixed.
@Mohit_Sharma advised me to post here, in case some of you guys might have any workarounds for this. Anyone else getting into this errors? How are you getting around it?
Our project is pretty screwed unless we find a way to deal with this situation.