---
title: Generation records
description: Understand saved generation history and troubleshooting retention.
---

Use [Operations and retries](/docs/operations) for short-lived request status and billing inspection. This page describes longer-term troubleshooting records and dashboard playback history.

Keep the `X-Request-Id` returned by `POST /v1/audio/speech` when contacting support.
Authorised administrators can inspect recorded customer requests for troubleshooting.
Request metadata, input text, processed text and diagnostic payloads are retained
together for ninety days, using UTC-day boundaries, when capture succeeds. Capture is best-effort: missing diagnostics do not mean the speech
request failed or was uncharged.

History is browsed by customer and date. New records appear after hourly background
export; processing backlogs or storage outages may delay it further. Daily account totals are retained for twenty-four
months from the usage date. Read those totals through [Usage](/docs/usage).

The dashboard's saved generation history is separate: it keeps the newest twenty entries
per generation type, for up to thirty days, including saved text and audio. Deleting an
entry schedules its stored files for deletion.

The current gateway does not expose `/v1/audio/generations/:id` or a generation-audio
retrieval endpoint. Ordinary API output is streamed, not automatically archived for
later download. Save the audio in your application if you need a durable copy.

If a stream is interrupted, preserve received audio as partial and keep the server
`X-Request-Id` separately from any client-supplied `Idempotency-Key`. Neither identifier
can restore missing audio. Missing diagnostics do not establish whether generation
completed or was charged; do not automatically submit another paid generation.

These limits do not control financial-record retention. Billing records remain separate
from troubleshooting content. See the [Privacy Policy](/privacy).