Closed johnsmith-gooddollar closed 1 year ago
@sirpy I've searched logs since 1 Jan 2022 - found only one more case. Both happened from 04/01/23 till today (12/01/23). Both have the same issue - contact not found. Both were created in the previous year (the second one at 02/08/22). Both have no logs about signup process.
account / crmId 0x3c304c7fc1b69ceba7c87f8350f999d47dc865fb 626d75bf45bb0352e08b4568 0xfc302220acbd314f71db58ac3b7d1d5b3c0ded13 61c7244e43bb039f778bb8c0
P.S. It looks like Logenties had been cut records before 1/1/23 off - could it be possible ?
@sirpy The issue still appears but with the same accounts. As we don't have full history about them, we still cannot research for the reason possible.
No new cases found. It looks like we have a few accounts "broken". Should we do something with that ?
@johnsmith-gooddollar i was filtering the logs by "ongage error" there are frequent 404 errors from contacts/by_email - according to the code it is supposed to ignore these errors
async getContactIdByEmail(email, logger) {
try {
const existingContact = await this.getContactByEmail(email, logger)
return get(existingContact, 'payload.id')
} catch (exception) {
if (404 !== get(exception, 'response.data.payload.code')) {
throw exception
}
}
so that seems broken.
otherwise we can close this issue after the above is fixed
the reason is that contect with ID 626d75bf45bb0352e08b4568 not exists at OnGage. Unfortunately i’m not able to reach how it’s possible. I’ve found account of this guy in mongo. He created it 30/04/22 but first logs with his account id are starting from 04/01/23. There’re no logs about his signup, nor about any further events. Maybe he removed then recreated account. Need more cases.