Candidate data being updated despite last user login indicating no recent login

[cazcam34]

Hi there, I have had two strange cases lately where the bio information was changed after intake. 229248 and 249782. On 249782, it seems the candidates information change replaced with his partners information, but on 229248, I cannot see any relationship at all and nationality, sex, name, etc have all been changed. Is there a way to do some investigation into what has gone on here? Thanks! <@U06RW10M30A> fyi

Slack Message

[cazcam34]

Hi team - I picked this up from the tc-software channel from Mari Christy. I have looked into this briefly, but it's late here and I am not back until Thursday (Aus time) so incase anyone else would like to pick it up here is what I have noticed.

So it seems candidate data is changing, such as name, gender, nationality... all fields that can be changed by a candidate. However on the two candidate's profiles they are both showing that the user was last logged in as further in the past, before the intakes were done - and so it's why Mari and Gabriella who completed the intakes know that the data changed after this date and are curious how if it appears the candidate's haven't logged in since.

When I looked into the DB for the two candidates I can see there is a discrepancy for candidate 249782 where the user's last login is listed as something, however the candidate was last updated by that candidate user themselves and on a more recent date. So the last login date isn't matching with updates, the last login being on 14/07/2024 but they last updated their candidate data on 1/10/2024 (after their intakes were completed on the 24/09/2024). See screenshot for the data. In the case of the other candidate, the most recent update to the candidate was done by user 215077 who is Mari Christy so it's harder to tell but it could have just been that Mari Christy made an update since the candidate.

So my suspicion is that the candidate's have updated their profiles since the intake but it doesn't reflect via the last login date for some reason...

Here's the SQL I used to generate the table in the screenshot for reference: select c.id as candidate_id, candidate_number, u.id as user_id, u.last_login, c.updated_by, c.updated_date from candidate c join users u on c.user_id = u.id where c.candidate_number in ('229248', '249782')