Exporting results
For offline analysis or sharing with stakeholders outside the platform, export evaluation results (and test application results) as async CSV exports delivered by email.
Large result sets make synchronous in-browser downloads unreliable, so exports run on the backend and the file lands in your inbox.
Where to export from
The Export button appears at the top of:
- The Evaluation Results table.
- The Test Application Results table.
Clicking it opens an Export configuration popup.
The export popup
The popup shows:
- Total rows in results — for the current table context (after any filters you've applied).
- Maximum rows exportable per export request — the configured system limit.
It includes two input fields:
- Number of rows to export — required. Defaults to
min(max_rows_exportable, total_rows_in_results). - First row index — required. Defaults to 1.
Both fields have help text explaining:
- The max-per-export cap.
- That you can export all rows by running multiple exports with different first-row indices.
So if your run has 12,000 rows and the cap is 5,000, you'd run three exports: rows 1–5000, 5001–10000, 10001–12000.
Submitting the export
When you confirm:
- The request is submitted to the backend.
- The popup tells you:
The results will be sent to you over email in 20–30 minutes.
For MVP, email is the only delivery channel — there is no in-UI export history or in-browser download today.
Audit logging
Each export submission creates an audit log entry with:
- Resource type — based on which table initiated the export.
- Action —
Results Exported. - Actor — the user who requested.
- Timestamp.
When export emails don't arrive
If you don't receive the email after the 20–30 minute window:
- Check your spam folder and any organizational email filters.
- Confirm your workspace email is correct.
- Re-submit the export.
System-level retries and deliverability monitoring exist on the backend, but UI-level retry isn't surfaced today.