Change Details

1. This is not used. 2. This is broken storage side (origin-visit-add does not deal correctly with it and it so happens there is no test around it so unfortunately it got detected by @douardda's run with the backfiller or something). 3. And finally, this will soon go away with T2310.

1. This is not currently not used in production. 2. This is broken storage side [1] 3. And finally, this is temporary as this will soon go away with T2310 [2] [1] origin-visit-add does not deal correctly with metadata (origin-visit-status-add does it well though). And it so happens there is no test around it... So unfortunately it only got detected by @douardda's run with the backfiller or something. It's good it got detected though ¯\_(ツ)_/¯ [2] we are currently phasing out multiple origin-visit fields including this one

1. This is not currently not used. in production. 2. This is broken storage side [1] 3. And finally, this is temporary as this will soon go away with T2310 [2] [1] origin-visit-add does not deal correctly with metadata (origin-visit-status-add does it well though). This is broken storage side (origin-visit-add doeAnd it so happens there is not deal correctly with it and it so happens there is no test around it s... So unfortunately it only got detected by @douardda's run with the backfiller or something).g. It's good it got detected though ¯\_(ツ)_/¯ 3. And finally, this will soon go away with T2310.[2] we are currently phasing out multiple origin-visit fields including this one