Hey @bamatic …
Prior to 3.12, Muting was performed on the server… so if an offline user submitted a mute or unmute report on their device, they wouldn’t actually see the affects until they synced that report up to the server, the server processed it, and they synced back down. Starting in 3.12, Muting and Unmuting are performed on-device for offline users.
In the sample you provided, all those Unmutes that happened within minutes of each other were from 2020. 3.12 was released on 28-July-2021 so hopefully you don’t see that issue happening after the date you updated to 3.12+.
The SQL below will tell you the version and time that each server upgrade started on your instance
SELECT
doc#>>'{tombstone,build_info,version}' AS app_version,
to_timestamp(((doc#>>'{tombstone,created}')::bigint / 1000)::double precision)::date AS upgrade_started
FROM
couchdb
WHERE
doc#>>'{tombstone,_id}' = 'horti-upgrade'
AND doc->>'type' = 'tombstone'