Multiple conversation_updated_at for same tag_id and conversation_id in conversation_tag_history table

Hello,

When I query the conversation_tag_history table, I noticed there can be multiple conversation_updated_at values for the same tag_id and conversation_id.
Usually the MIN(conversation_updated_at) value is accurate, but I wonder how this can be the case?
It happens frequently so I don’t think it’s because someone is removing a tag and adding it again, but I can be mistaken.

Thanks in advance!