Session Exports
A session export packages a whole session as a single ZIP archive: the session record, its template, a manifest, and one file per node output. Exports are produced in the background, so they have their own queue. Open Data, then Session Exports (/admin/sessions/exports).
You start an export from the Export session button on any session detail page. This page is where you watch it build and download it once ready.
The export queue
Each job shows its session and a status.
| Status | Meaning |
|---|---|
| Queued | Waiting to start |
| Running | Building the archive. Progress shows outputs written against the total |
| Ready | Finished. Download it here or from the session page |
| Failed | The export did not complete. Retry it |
| Expired | The archive has passed its retention window and been removed |
Lifetime and size
A ready archive is kept for seven days after it completes, then removed automatically. Download it before then, or export again.
Large sessions produce large archives. A session with many outputs takes minutes to build and can be several gigabytes, so the session page warns you before it queues the export. Unreadable outputs are skipped and flagged in the archive manifest rather than failing the whole export.
Export a session before deleting it if the capture may be needed again, for example to reprocess it on a later template.