Model Call Records
The calls a workflow step or an assistant conversation makes to a model are recorded in your account's storage: the request as it was sent, the answer, the tokens, the timing and the error of a failed call. They are the way to find out why a model answered as it did, after it happened. Your documents, values and tool results in them are your data. Our own prompt text and tool definitions in them stay ours and confidential.
What is kept, and for how long
| Records of | Kept |
|---|---|
| A transaction | The last two runs of each step per document, until the transaction is deleted. A run from the start makes new documents, so the records of earlier ones stay too. Deleting one document or page from a transaction leaves its records, and a Redact step, which cleans what you export, leaves them too. |
| An assistant conversation | At most 30 days, and they go with the conversation. |
A record says which page an image came from and does not copy it. Recording is best effort: a record that cannot be written never fails the call. Calls that belong to neither, such as the prompt helper or model tests, are not recorded.
Download them
The records come as a zip, through the API or the CLI. There is no screen for them.
da model-calls download <transaction id> -o calls.zip
da model-calls download --conversation <session id> -o calls.zip
The zip holds the pages the calls sent, including those of Memory examples and of any transaction an assistant conversation read. They are the pages as they are now, so a page changed since looks different from what the model saw, and a page deleted since, or one you may not download, is left out and listed in manifest.json. Add --no-pages to leave the images out.
The zip is a debugging tool, not an export step, so Redact does not apply to it: its text is what the calls carried, and it can show values a Redact step removed from your documents. Handle it as you would the original documents.
| Route | Needs |
|---|---|
GET /transactions/{transaction_id}/model-calls | transaction.download_results and memory.view_learning |
GET /assistant/sessions/{session_id}/model-calls | assistant.settings.manage across the tenant, for any conversation |
Sending them for a support case
On a self-hosted or managed deployment, if support asks for the records of a transaction or a conversation, an administrator runs the command above and sends the zip through your usual support channel. Send only what the case needs: the zip holds your documents' text and page images and the examples from your Memory, and our confidential prompts.
On our cloud service, support reads the records a case needs as the Data Processing Agreement allows.