🐞 Bug: Lookup history inconsistent with analytics across sessions

[shrmaanubhav]

Summary

• When a user performs a lookup, it appears immediately in History but not in Analytics.
• After logging out and logging back in, the lookup appears in Analytics but disappears from History.
• This creates inconsistent and confusing behavior across sessions.

Steps to Reproduce

• Log in to the application.
• Perform a lookup.
• Observe that:
  • The lookup appears in History
  • The lookup does not appear in Analytics
• Log out.
• Log back in.
• Observe that:
  • The lookup now appears in Analytics
  • The lookup is missing from History

Expected Behavior

• Lookups should appear consistently in both History and Analytics
• Logging out or logging back in should not affect persisted history
• History and Analytics should be derived from the same persisted data source

Suspected Cause

• History and Analytics appear to use different read paths or filters, possibly:
• Session-scoped filtering (e.g. session_id)
• Login-time–based filtering
• Mismatched flags or lifecycle conditions
• Although lookup events are persisted to the database, the history query after login does not return them consistently.

Impact

• User confusion due to disappearing data
• Reduces trust in analytics accuracy
• Makes debugging user activity harder

[Apoorv012]

Assign

[SohamSDA]

Claim

[shrmaanubhav]

/info

[OpenGitBot]

User	Repo
Apoorv012	Loktantra (1), CareerCraft (1)
SohamSDA	Alum-X-Frontend (1)
shrmaanubhav	0

[shrmaanubhav]

assigned to @Apoorv012

[shrmaanubhav]

@Apoorv012 Please complete the task by EOD