Session Timelines

Where Analytics tells you what a hundred sessions look like together, Timelines tells you what one session was actually like. Pick a run and ARC replays it in order: when the game started, every hint sent and by whom, each objective completed, the devices that fired, the help requests, and how it ended.

This is the page you open when a customer disputes something, when a room behaved oddly and you want to know why, or when you are coaching a member of staff through a run that did not go well.

Finding a past game

The page is a two-pane workspace: the list of sessions on the left, the detail of whichever one you select on the right. On a narrow screen the two stack.

1. Pick the game in the game picker at the top of the page. If the room has been shelved, turn on Show retired games in that menu first.
2. Set the date range in the dock — 7 days, 30 days, 90 days, All time, or a Custom From/To pair. It starts on 30 days.
3. Narrow by outcome if it helps, using the wins and losses chips.
4. Click a row in the session list.

Reading the session list

The list header tells you how many sessions match your filters. Each row shows:

Staff with edit access also get a More actions menu on each row, holding Edit session and Delete session.

If nothing comes back, ARC says which kind of empty it is: No sessions match the current filters suggests widening the date range, while No retained Timeline details are available means the detail for those runs has been cleaned up — the sessions still count in Analytics, but their minute-by-minute record is gone. That is set by the retention rules further down this page.

The session detail

Select a row and the right pane fills in.

At the top

The date and time of the run form the heading, with the mode (Live, Testing, Retired) and the staff member’s name beneath it, and a large outcome pill to the right. If the session captured any Moments, a Moments button sits alongside, with the number of captures on it.

The facts

A grid of the essentials: Duration, Hints, Players, Staff, Team (when a team name was recorded), Started, and Ended.

The hint figure sometimes carries a small qualifier, for example ”n sent”. That appears when the recorded hint count differs from the number of hints ARC actually delivered — in other words, when staff nudged the count up or down by hand in Session Details. Hover it for the full explanation. Underneath, a By type row breaks the hints down into Text, Image, Video, Audio, TTS, and Verbal.

What happened

The heart of the page: an ordered list of everything ARC recorded during the run. Each row carries a category badge, a plain-language summary, the time of day, and the elapsed time into the game, so “+18:42” tells you where in the run it landed.

Badges cover the whole life of a session — GAME STARTED, HINT, OBJECTIVE COMPLETED, HELP REQUEST, DEVICE, and GAME SUCCESS or GAME FAILED at the end, among others. Rows often add a subline with the detail — the objective involved, or “By name” for the staff member who did it.

Two tabs sit above the list:

• Session history — everything.
• Staff actions — just the things a person did: hints sent, objectives marked, quick actions pressed, time adjusted.

A count in the corner reads ”n of n events” so you always know how much the filter is holding back.

Digging deeper

When a run has diagnostic rows recorded, a Troubleshooting checkbox appears with a count of them. Switching it on adds the technical detail and unlocks two more tabs, Automations and Readiness.

With troubleshooting on, rows can expand. A row headed ”n details” opens to show what actually ran underneath — the steps in an automation, the actions in a scene, the device changes, or how many automations were checked against an event, how many triggers did not match, and how many were blocked by conditions.

Automation rows also carry a via automation chip. Click it and the timeline narrows to just that one automation run, with a banner telling you what you are looking at and a Clear filter button to come back out. It’s the fastest way to answer “what did that automation actually do?“.

Correcting or removing a session

Staff with edit access can fix a record after the fact from the More actions menu on a row.

Edit session adjusts the saved summary: the Staff member, a Staff label, the Team name, the Player count, and the Hints used. If you type a player count above the room’s team size limit, ARC shows a gentle note asking you to double-check it is not a typo — it still lets you save. If the session was recorded against a name that is no longer in your staff list, the picker offers to keep that name rather than losing it.

Delete session removes the archived session from analytics for good. ARC asks you to confirm, and there’s no undo.

Moments

If a session captured photos or clips from the room, the Moments button in the detail header opens them. Moments are set up by a builder in the Editor — an automation decides when a capture happens — and reviewed here or on the Control page while the game is still fresh.

Timeline & History

The third group in the dock holds one button — Timeline & history — and it opens a drawer that applies to all games at your location, not just the one you are viewing. It is available from both Analytics and Timelines.

The status panel

At the top, a health readout for your game history: a state of Healthy, Preparing, Needs attention, or Unavailable, plus counts of Permanent sessions, Timelines retained, and Games ready.

Retention

This is where you choose how long ARC keeps the detail. Two settings:

Timeline detail retention governs the minute-by-minute record you read on this page. Out of the box ARC keeps it forever — nothing expires unless you decide it should. If you do pick a number, the shortest window offered is 30 days.

The important part: expiring timeline detail does not delete your history. Your permanent session record, Analytics, future leaderboards, Pace, and Assist learning all survive. What goes is the ability to open one specific old run and read it event by event.

Troubleshooting retention covers the short-term diagnostic evidence behind those runs — the kind of thing support asks for. Removing it changes nothing about your game history or your retained timelines.

Selected game

A collapsed section showing the history for whichever game you are currently viewing: Permanent sessions, Timelines retained, and the Oldest retained Timeline. It also holds Clear history, which permanently deletes all session history for that game — afterwards its Analytics, its Timelines, and everything else in Insights for that room will be empty. ARC asks you to confirm and warns you that it can’t be reversed.

Storage and maintenance

A read-only section for when you want reassurance that the record is sound: the database size, the last integrity check and whether it passed, the last successful backup, when maintenance last ran and when it will run next, how many timelines were removed and how many were held back for safety, and any errors. A Refresh status button re-reads it, and if something needs attention a link appears to the related system logs.

Where to go next

• Analytics — the numbers across many sessions, and the Reporting criteria.
• Insights — the area overview and who can see what.
• Running a Game — Session Details, Moments, and the run this page records.
• Hints and Objectives — the actions that make up most of a timeline.