Because we only listen to the row itself, the only change events that trigger a re-render are property additions / changes or adding / removing children.
We can fix this by doing a walk of all Block children when opening up subscriptions & on the subscription update. This might be something we could add to the notion-py module itself and PR in.