I'm interested in how Quiver is going? It looks like this is your main revenue stream? I've looked at it before and been unsure what it does, and trying it now it doesn't seem to work for us (no requests ever reach quiver with the GraphQLQuiverCloudBackend). Is it production ready, or is it in preview at the moment?
Edit: so the issue was that we had an extraneous trailing comma, which was turning a string (deprecation reason) into a 1-element tuple, which was then failing an assertion in the AST serialisation within graphql-core, however this assertion was being silenced by one of the backends - either the decider or the Quiver backend.
Edit: so the issue was that we had an extraneous trailing comma, which was turning a string (deprecation reason) into a 1-element tuple, which was then failing an assertion in the AST serialisation within graphql-core, however this assertion was being silenced by one of the backends - either the decider or the Quiver backend.