You're close! Turns out the reason we didn't catch it in testing is because the problem only triggered if you either (a) had no services saved, or (b) hadn't edited them since we migrated where the settings were stored in order to allow multiple accounts per service type.