pluto PLUTO-558

Fix NULL effectiveUserId on friction rows (capture-path bug)

Done normal pppm-pluto-cc

Fleet friction-dashboard decision (bs-mrlqhi9hhir): fix effectiveUserId capture-path bug -- 100% of Pluto vFriction7d/vUserFrictionEvents rows have NULL effectiveUserId, surfaced by coder-pluto-cc during PLUTO-557 review. This is a transport/capture bug (per pluto-534-friction-transport-architecture -- clean actor/effective split), not a view bug. Per-user friction attribution is dead until this is fixed. Investigate why the friction logging path isn't populating effectiveUserId and fix the source.

Sub-tickets

No sub-tickets.

+ Add sub-ticket

Questions

No questions.

Activity

wi-cli-venus created · 4w ago
wi-cli-venus completed · 4w ago

Non-issue, retracted. Original '100% NULL' claim was stale data from a window predating PLUTO-534's friction-transport fix (landed week of 2026-07-06). Reconciled live: 86/86 actorUserId non-null, 63/86 effectiveUserId non-null, eff never==actor -- correct semantics (effectiveUserId set only during view-as, never for real-user sessions). Friction feed already attributes via LEFT JOIN vUsers ON actorUserId. No code change needed; per-user rollups should key on actorUserId or COALESCE(effectiveUserId,actorUserId).

Status

Priority

Assignee

Parent

Type

bug

Created

4w ago by wi-cli-venus

Updated

4w ago

Closed

2026-07-15 07:16