According to the GraphQL spec, [errors on non-nullable fields propagate to their parent](https://spec.graphql.org/September2025/#sec-Handling-Execution-Errors). This works correctly for nested fields but not for root level fields: ``` @Test fun `errors during operation execution should not stop other operations`() { val response = testedSchema.executeBlocking( """ { number1: number(big: true) exception1: exception nullableException1: nullableException number2: number(big: true) exception2: exception nullableException2: nullableException } """.trimIndent() ) response.deserialize()["data"] shouldBe mapOf( "number1" to 10000, "nullableException1" to null, "number2" to 10000, "nullableException2" to null ) } ``` Actually, errors on _non nullable_ operations _should_ stop other operations and return `{ data: null }`. See also: - https://github.com/graphql/graphql-spec/issues/1182 - https://github.com/graphql/graphql-spec/issues/277 Further reading: - https://github.com/graphql/graphql-spec/pull/1015#discussion_r1102144722 - https://github.com/graphql/graphql-spec/pull/1184 - https://github.com/graphql/graphql-spec/pull/1183 - https://github.com/graphql/graphql-spec/pull/894#issuecomment-1153716690 - https://github.com/graphql/graphql-spec/pull/1163#discussion_r3174521881 - https://benjie.dev/graphql/nullability
Activity
feat!: support fragments on query level
stuebingerb commentedon Jun 15, 2026
Will be fixed with fragment support on query level
feat!: support fragments on query level (stuebingerb#650)