Sessions
A Session is one run of a session template over one batch of data. The Sessions section lets you find a session and check what happened to it, node by node. Open Data, then Sessions (/admin/sessions).
The Control Centre shows you the state of processing and the location of stored artefacts. It does not open the data itself. This lets you confirm that uploads arrived, that outputs were stored and whether a fault occurred. Reading the results is the dashboard’s job.
Finding a session
Search by name, simulation, email or id, and filter by project and session template. Sort by name or date. New session creates an empty session from a template, which is useful for confirming a freshly imported template builds the expected node graph.
The table shows each session’s name and id, its project and template, the simulation name, the owner and when it was created. Select a row to open it.
The session detail
The detail page shows the session name, its id, and three actions: Freeze scheduling, Delete session and Export session. Below them are the tabs.
Overview
The Overview tab shows the node count and how many have completed, the owner, the creation time and the project. A row of cards summarises storage: the number of outputs, the uncompressed size, the amount stored on disk, the average output size and the dominant content type. Index coverage and Reachability bars show how much of the session has been scanned and read. A Content types breakdown and a Metadata tree view follow.
The stored-on-disk figure is where you see which sessions are consuming space. The largest sessions are where you reclaim it when the object store fills.
Live DAG
The Live DAG tab draws the session’s node graph and colours each node by state, refreshing every few seconds. It is the quickest way to see where a run stalled or failed. Drag to pan, scroll to zoom.
Nodes
The Nodes tab lists every node instance with its state. Read a node’s status details when it fails.
| State | Meaning |
|---|---|
| Never began | Created, no task has run yet |
| Pending | Queued and waiting for a runner |
| Processing | A runner is working on it now |
| Succeeded | Finished, output available |
| Failed | The last run failed. Open the node for details |
| Suspended | Paused by the platform |
An input node that succeeded with zero outputs usually means no upload arrived. A processing node accumulates outputs over time, so several rows for one node is normal.
Dimensions
The Dimensions tab lists the dashboards the session published. Each Dimension shows its name, scenario, dashboard version, the number of users and the scenario window, with Details and Open actions. Use this tab to confirm a session publishes only the dashboards you expect. Unexpected dimensions, for example a leftover test dashboard, show up here before they reach a trainee’s session list.
Operator actions
Freeze and unfreeze
Freezing a session is a reversible handbrake on scheduling. While a session is frozen the platform creates no new tasks and runners cannot claim its queued tasks. Nothing is deleted. Unfreezing restores the previous state and the backlog becomes claimable again. Freeze a session that is in a churn loop, fix the cause, then unfreeze.
Export
Export session packages the whole session as a ZIP archive: the session record, its template, a manifest and one file per node output. Exports run in the background and large sessions take minutes. A session with many outputs warns you first, since the archive can be several gigabytes. Track and download it on the Session Exports page.
Delete
Delete session is irreversible. It removes the session record, its node instances, outputs, user links and stored objects, and any bulk analytics data written for it. Export the session first if it may be needed again.
Deleting the heaviest sessions is how you reclaim object store space when it runs low. See session retention for the policy-driven alternative that removes old outputs automatically.