Find out why some users do not have a timezone while their partners do
longd3 opened this issue · 4 comments
(Alleged) Scenario: User has an account properly paired to a sense, timezone is detected. At 1 point, the same sense is paired with another account and then this second account's timezone is not detected and prevents sense data from being processed.
This issue has been patched by a routine cron hello/hello-admin#417 that calls api #1029 but we are still interested in finding the root cause.
List of users patched by the cron:
1523, 1773, 25504, 26066, 35734, 26070, 35786, 35790, 36035, 36093, 26072, 36876, 29236, 34864
It's still happening today, latest case is 34864 (patched at 4:34pm)
As discussed with @jimmymlu, it could be a client issue so I am assigning it to Jimmy, feel free to correct me otherwise
So i looked at 8-9 cases listed above and they all have a similar pattern:
- account w/o time zone was because user never fully set up the account. either b/c the set up failed or user simply abandoned it and created another account.
- in cases where user never even got as far as linking the account to Sense, according to mixpanel, the user's account somehow magically got paired (i assume it was done manually by someone), which would suggest the clients are not the cause of the missing time zones
I didn't look at every single case, but in all 8-9 cases, it was the same pattern so i stopped. Reassigning this bug since afaik, it is not a problem with the client not setting the time zone
Admin pairing provide 3 timezone options: Pacific, Shanghai and GMT. So I am pretty sure if helped by pairing via admin, we should see one of those tz.
Btw this issue seems to be rarer these days, last case seen was
admin-logs-botBOT [4:34 PM]
Successfully updated timezone by partner for account 34864
I added logs to admin pairing so we can correlate if necessary in the future
Thank you both for looking into this
Close as this is not happening anymore. We still have a cron job to patch if it happens