​

Video room history

The History page lists your completed video sessions in one place — every ended scheduled room, most recent first, with its duration, recording, and participants. Where the live Rooms list shows what is scheduled or in session now, History shows what already happened, so last quarter’s review call stays reachable after the live list has moved on. This page covers the dashboard surface. For the underlying data model — how sessions are stored and swept — see The video room model.

​

Where the page lives

In the dashboard, open Voice → Video → History. The page is available to the owner, admin, and developer roles. Each session row links to a detail view with the full record: the participants roster, the room details, recording playback, and the transcript panel.

​

How long sessions are kept

Ended sessions are retained for 90 days by default, followed by a two-week grace window before they are hard-deleted. Your organization can override the window with the video_room_retention_days setting — minimum 7 days — as described under Limits on Video: rooms, embeds, recording, and broadcast. Until the window passes, a row on this page stays complete: participants, duration, recording, and transcript all remain available.

​

Find a session

With many ended sessions, finding a specific meeting is a lookup problem, not a scrolling problem. The page loads the 100 most recent ended sessions and exposes a search field that filters them by case-insensitive match on the room name or id. The list refreshes as you type; a Clear filters action appears whenever a search is active. Narrow the list first, then read a row:

• Search matches the room name or id — try a client’s name or the room id from an API response.
• Load more reveals the next batch of rows when the first screen is not enough, with a running Showing N of M count.
• Refresh reloads the list, so a session that ended a moment ago appears once its final state has settled.

​

Read a session row

Each row carries the room name plus the badges that let you triage at a glance:

• End-reason badge — how the session closed: a clean finish, an operator-forced close, an idle-timeout cleanup, or an error termination. A session nobody ever connected to is flagged (for example Failed) so it does not read as a completed call.
• Duration badge — the session length, derived from start to end when a participant ever joined. Never-joined sessions show no duration, so a session nobody entered never reports a phantom length.
• Recording badge — shown when recording was enabled for the room.
• Ended timestamp — the end wall-clock time, rendered in your own timezone.

When recording was on, the row can also carry recording-health signals: Recording missing (or Recording degraded) when the post-recording quality check found the artifact unusable or impaired, and a Preview badge when a first-frame snapshot is available. Treat these as the first place to check before you promise a recording to someone.

​

Open the recording and the transcript

A recorded session gets a Recording action on the row. It opens the playback widget, which keeps the playback link refreshed automatically, so a long review session does not break with an expired URL. Click the room name to open the detail view. Below the recording it carries the transcript captured during the session — the transcript panel is where you search what was actually said and, where your data-policy allows, purge it. Recordings are attached to the session only when recording was enabled at room creation or started during the session — see the Recording section of the video channel page for how enablement and per-participant consent work. A session without recording shows No recording.

​

Export or reopen a session

History surfaces are reporting views — the page never places an outbound call or message. To reuse a recurring meeting, reconvene it as a new session of the same scheduled room rather than recreating the room: the reopened session appends a new history entry instead of overwriting the old one, so the audit trail across occurrences stays intact. For data export, pull sessions through the Video API — GET /video/rooms-scheduled?status=ended returns the same rows the page renders, so a retention report or a compliance export can be automated against the endpoint.

​

What to check when something looks wrong

• A 404 on playback usually means the room’s recording never finalised — confirm the Recording badge was present on the row.
• A Recording missing or Recording degraded badge means the quality check already found the artifact unusable or impaired; treat the badge as the confirmation rather than a playback failure.
• An empty page right after a meeting that just ended usually clears on the next refresh — the list reloads itself every minute.
• A session missing entirely is almost always the retention window: once the configured window plus the grace period passes, the session rows are removed. Check video_room_retention_days on your organization.

​

Where to go next

• Video room model — scheduled versus ad-hoc rooms, the session record, and how the retention sweep runs.
• Video meetings and conferences — create and run the rooms whose sessions land here.
• Registration-gated video webinars — registrant reports and check-in for the sessions you gate.
• Video API reference — the endpoint surface behind the list and detail views.