This avoids re-fetching all origin visits / origin visit statuses when new visits
happen. This is only a workaround. When voiding the cache, the error will still happen.
We need to rework the overall visit/visit-status fetching, the code is hard to follow
through.
Discussing with @anlambert, there is yet another improvement we could lift (independently
from this).
Related to T3905