So, upon further review, it seems the code will only update changes in default category notifications on a user group… see here for the change handling and here for the db update.
This means that if, for whatever reason, your initial update process to the group does not update the existing user objects, resaving the group (even with changes) doesn’t necessarily trigger the updates for the default category notifications for the group members.
I’m not entirely sure why my initial update process didn’t trigger, but since I used an api call, not the admin, I may have submitted an incorrect ‘update_existing_users’ parameter (i json dumped a python ‘True’ value).
Regardless, I did manage to resolve this issue.
Solution:
- Go to the user group admin, reset any category defaults which do not seem to be updated yet on users. (Ex: if group members don’t properly have a mute on a ‘Support’ category, then remove that category from the muted categories. If that category used to be in ‘normal’, then reset to ‘normal’)
- Save the group and say no to ‘update existing users’
- Change the group category notifications to the desired category notifications
- Save the group and say yes to ‘update existing users’
Voila, it should now be good!
FWIW, i have no judgement on if this behavior is the right behavior or not. However, it could probably be documented 