After some back-and-forth with SS customer service (which was very responsive, helpful and friendly) they admitted the issue is on their end. They said they will try to address it in a future update. No timeline was given.
So, no fix, but at least I know it wasn't my code.