There's no clear cause behind this bug, as there's no user-specific logic for this in the backend. It isn't reproducible, so I'm making this just in case it persists.