Recover from subscription error

[Meemaw]

When an error happens during subscription resolving, the underlying subscription seems to be closed. I would like to change this behaviour to keep the connection open.

One common case where we have seen an error happen is when we return data that doesn't match nullability constraints on the schema. Error will look like this:

The field at path '/activities' was declared as a non null type, but the code involved in retrieving data has wrongly returned a null value.  The graphql specification requires that the parent field be set to null, or if that is non nullable that it bubble up null to its parent and so on. The non-nullable type is 'Sale' within parent type 'Subscription'

This is not great, but it can happen and when it does, we would like the subscription to stay open. Any suggestions on how to customize that? We added .onErrorContinue to the Flow that we return to the @DgsSubscription, but I think that's not called because you are doing operations on the flow after that call.