@custom resolver results in status code: 400

Sorry, I have not had time to duplicate a custom graphql query yet.

Awesome! Glad the bug was already squashed!

This from what I have seen varies a lot. If it is a bug that is not a breaking change, sometimes it can be cherry picked into a minor release. If it is a breaking change or new feature then it will go into the next quarterly(?) release after it has been fully tested and merged. The next major release (20.11) is set for “early November” from what I have been informed on Discuss.

Are you using Slash GraphQL? If so, presenting a (not) working example of the issue may help.