Sessions
Sessions are persisted chat conversation threads. They allow:
- continuing a conversation over multiple turns
- reviewing what users asked and what the assistant answered
- capturing feedback and sources per message
What a Session Contains
Typical session data includes:
- a unique
session_id - timestamps (created/updated)
- optional user identity information (admin user or public username)
- a list of messages:
- user messages (prompts)
- assistant messages (answers)
- sources/citations (if enabled)
- feedback (if submitted)
How Sessions Are Created
Sessions can be created in different ways depending on the entry point:
- Admin-driven testing in a KB detail embedded chat
/ai-chator/ai-chat/{kb_id}public-style chat flows- API-driven chat queries that specify or omit
session_id
Operational behavior:
- If
session_idis provided and valid, the conversation continues in that session. - If
session_idis missing, the system may create a new session automatically.
Sessions List Page (Admin)
Common actions on the sessions page:
- browse sessions (often paginated/limited)
- open a session to see message history
- filter by knowledge base or user (if supported)
- delete a session
Message Review Tips
When reviewing a session:
- Start from the user question: is it well-formed?
- Inspect sources (if visible): did retrieval pick relevant chunks?
- Check feedback: is there a pattern (too slow, irrelevant, lacking sources)?
Deletion and Retention
Deleting sessions is useful for:
- removing test data
- complying with retention policies
- cleaning up unused/obsolete sessions
Important:
- Session deletion usually deletes its messages too.
- Treat session deletion as irreversible unless your deployment has backups.
Troubleshooting
Session exists but messages are missing
Common causes:
- filtering (some UIs hide system messages or certain roles)
- partial loads (lazy loading/pagination)
- data consistency issues
Recommended checks:
- refresh the session view
- verify via API (see
/docs/api) whether the messages exist
Feedback isn’t showing
Common causes:
- feedback was never submitted
- UI is reading feedback from a different endpoint than the one used to write it
- permissions/auth issues
Recommended checks:
- open the message in tracing (if available)
- confirm feedback API calls succeed (Network tab)