Any idea how to avoid this problem?
It’s an expected behavior. And as far as I know, there is no solution on that.
A solution on that may require a fundamental change in how GH processes clusters.
Some mechanism for documents inside clusters to expire the cluster object which contains them is probably a good idea to keep in mind when designing the next version yes.