Some batch job (incorrectly?) deactivated certain sessions for whatever reason?<p>Getting "someone ran a one off job or migration that didn't do the right thing" vibes.<p>For instance, they could have tried implementing a "deactivate recovery phone numbers if this dataset from cell providers show the owner changed" that went wrong