Interdependent types lead to infinite loop with cacheExchange

[jaulz]

I have two types that are interdependent of each other, e.g.:

type A {
  id: ID
  name: String
  b: B
}

type B {
  id: ID
  name: String
  a: A
}

query ReadB {
  b {
    id
    name
    a {
      id
      name
    }
  }
}

query ReadA {
  a {
    id
    name
    b {
      id
      name
    }
  }
}

Now, if I update A and request the response including information about B:

mutation UpdateA {
  updateA {
    id
    name
    b {
      id
      name
    }
  }
}

cacheExchange will now trigger ReadB which again triggers ReadAwhich again triggers ReadB...
Is there any way how I can prevent it?