Closed
Bug 2005406
Opened 8 months ago
Closed 7 months ago
Clarify sessionId vs flowId terminology for AI Window Security Layer
Categories
(Core :: Machine Learning: General, task)
Core
Machine Learning: General
Tracking
()
RESOLVED
FIXED
People
(Reporter: rconcepcion, Assigned: rconcepcion)
References
(Blocks 1 open bug)
Details
(Whiteboard: [genai])
The security layer uses sessionId to identify AI Window sessions. Telemetry uses flowId for a similar concept. We should check with @thasan whether these refer to the same thing, and if so, align on consistent terminology to avoid confusion.
Reference
toolkit/components/ml/MLTelemetry.sys.mjscontainsflowId
Acceptance Criteria:
- Clarification from @thasan on whether
sessionIdandflowIdare the same concept - If they are the same, update security layer code and docs with consistent terminology
Updated•8 months ago
|
| Assignee | ||
Comment 1•7 months ago
|
||
Confirmed with @thasan: flowId comes from pipelineOptions.flowId if provided; otherwise MLTelemetry auto-generates a new UUID. Each feature owns its flowId lifecycle (ephemeral vs persistent). For AI Window session-level tracking, AI Window should generate a persistent ID per session and pass it via pipelineOptions.flowId. No terminology changes needed in the security layer at this time.
Status: NEW → RESOLVED
Closed: 7 months ago
Resolution: --- → FIXED
| Assignee | ||
Updated•7 months ago
|
Assignee: nobody → rconcepcion
You need to log in
before you can comment on or make changes to this bug.
Description
•