The CustomerAddressRepository uses a CustomerAddressRegistry which will cache entities on load. If the updates happen in a different thread, there is a possibility that stale data is returned.
However, we still want to use the repository instead of using the resource model to preserve modifications added by plugins.
Therefore, manually removing the entity from the registry should guarantee that it is always loaded from the database.
This is the same solution as used for the customer entity.
The CustomerAddressRepository uses a CustomerAddressRegistry which will cache entities on load. If the updates happen in a different thread, there is a possibility that stale data is returned. However, we still want to use the repository instead of using the resource model to preserve modifications added by plugins.
Therefore, manually removing the entity from the registry should guarantee that it is always loaded from the database.
This is the same solution as used for the customer entity.