Hi @minhaj we are also looking at this issue to be fixed. In the absence of errors thrown during add/update mutations for non-nullable fields marked with (!), it can very quickly lead to inconsistent data while the queries throw an error. We are trying to be vigilant around this issue during data creation/updates and would like to know a timeline around this getting shipped?