Deleting Run Transcripts

Every automation run keeps a transcript: the conversation with the AI, the run's input, its final answer, and the inputs the automation sent to each tool. You can delete transcripts for one run, for several runs at once, or for every run of an automation, and you can have each run's transcript deleted automatically once the run is over.

A deleted transcript is gone from StackJack and from our AI provider. You cannot undo a deletion.

Who can delete transcripts

Only organization owners and administrators can delete transcripts or change the automatic setting. This holds on every screen and from your AI assistant. Members, including members who can build automations, see whether a transcript is scheduled or deleted, but they get no delete buttons, and the automatic setting is read-only for them. An automation can never delete transcripts through its own connection.

There is one exception. Deleting a whole automation also deletes the transcripts of its runs, so anyone who is allowed to delete the automation also deletes those transcripts. The confirmation says so before you click. See Deleting an automation below.

What is deleted and what stays

When a run's transcript is deleted, StackJack deletes:

• the conversation, from StackJack and from our AI provider;
• the run's input (for example the webhook body that started it), its final answer, and its error text;
• the inputs the automation sent to each tool, and the details of any check that quoted a tool's response;
• large tool results that StackJack stored as separate files and named in the conversation;
• the run's recorded test data, if run recording was on.

The run record stays: its status, its times, the credits it used, and which tools ran and whether they succeeded. Your run history and your bills do not change.

Some copies live outside the run, and a transcript deletion does not reach them. The confirm dialogs list them: emails already sent, test scenarios you saved from the run, what the automation saved to its memory, and logs StackJack keeps to run the service. Our AI provider may keep a conversation it flagged for safety review for up to 2 years.

A run whose transcript is deleted cannot be re-run or saved as a test scenario, because its input and recordings are gone with it.

Delete one run's transcript

1. Open the run from Run History to reach its run detail page.
2. Click Delete transcript in the header. The button appears only on a run that has finished, and only while no deletion exists for it yet.
3. Read the confirmation and click Delete transcript again.

The confirmation reads: "This permanently deletes the conversation, the run's input and final answer, and the tool inputs, from StackJack and from our AI provider. The run record stays. You cannot undo this."

A run that is still running cannot be deleted. The button appears once the run finishes.

Delete several runs at once

1. Open Run history for the automation.
2. Tick the box beside each finished run whose transcript you want to delete, or tick the box in the header to select every finished run shown. Runs that are still running have no box.
3. Click Delete transcripts. The button shows how many runs you selected.
4. The dialog counts the runs first:
   • how many will be deleted now;
   • how many will be deleted when their billing is final;
   • how many are still running and will be skipped;
   • how many were already deleted;
   • how many were already scheduled for deletion (shown only when there are some).
5. Type DELETE TRANSCRIPTS in the box, then press Enter or click outside the box. The Delete transcripts button turns on.
6. Click Delete transcripts.

If every selected run is already deleted, scheduled or still running, the dialog says "There is no transcript left to delete."

Delete every transcript of an automation

1. Open the automation's detail page.
2. In the Run transcripts card, click Delete all transcripts.
3. The same dialog counts the runs. Type DELETE TRANSCRIPTS, press Enter or click outside the box, and click Delete transcripts.

Runs that are still running are skipped. Delete them again after they finish, or turn on automatic deletion.

Delete transcripts automatically

Automatic deletion is a setting on each automation, and it is off until you turn it on. You find it in two places:

• the Run transcripts card on the automation's detail page, where the switch saves as soon as you flip it;
• the Guardrails and consent card in the builder's Guardrails & Deploy section, where it saves with the automation.

The setting reads: "After each run finishes and its billing is final, StackJack deletes the run's conversation, its input, its final answer and the tool inputs, from StackJack and from our AI provider. The run record stays: status, times, credits used and which tools ran. A deleted run cannot be re-run or saved as a test scenario. Turning this off stops deleting runs that are not already scheduled. Only owners and administrators can change this."

Two things to know:

• It covers runs that finish after you turn it on. Earlier runs keep their transcripts. Use Delete all transcripts for those.
• Turning it off stops new deletions only. A run that was already scheduled for deletion is still deleted.

If run recording is also on for the automation, the card warns: "Recorded test data is deleted with each transcript, so these runs cannot become test scenarios."

If someone who is not an owner or administrator changes the setting in a draft, for example through the chat assistant, StackJack refuses the save and the builder shows why. Nothing is changed silently.

When the deletion happens

A deletion is not instant. StackJack waits until the run is fully over and its billing is final, then deletes the transcript from our AI provider and from StackJack. That usually takes less than an hour after the run ends. A run on your Azure Foundry, or a run that stopped before it reached our AI provider, waits a little over an hour after it ends, so that the run's own last steps finish first.

The run detail page shows where the deletion is:

After a transcript is deleted, the run's transcript card shows the deleted sentence instead of the conversation, and the input and summary areas say "Deleted with the transcript".

If a copy stays in your own Anthropic account

If your organization runs automations on its own Anthropic key, the run's conversation lives in your own Anthropic account. StackJack deletes it there with your key, even after your Agent Runner plan has ended. If your key no longer works (it was removed from StackJack, or revoked or restricted in Anthropic), StackJack still deletes its own copy, and the page names the session it could not reach:

1. Open the Anthropic Console and delete the session the message names.
2. Or, once your key works again, click Try again on the run's page. StackJack deletes the session with your key.

StackJack finds the large tool results it stored for a run by reading the run's conversation, and it cannot read a conversation it cannot reach. So the message also says: "Large tool results stored for this run are deleted when deletion can finish." They are deleted when you click Try again with a working key, or when your organization is deleted.

Deleting an automation

Deleting an automation also deletes the transcripts of all its runs, from StackJack and from our AI provider. The confirmation says: "This also deletes the transcripts of its runs, from StackJack and from our AI provider." Runs that are still running are deleted after they finish. The same applies to discarding a staging copy.

Deleting your organization

When your organization is deleted, StackJack first deletes the transcripts of your automations' runs and switches your automations off while that finishes. The organization deletion waits for it for at most 24 hours; it normally takes minutes. A copy in your organization's own Anthropic account that StackJack cannot reach in that time stays there. When the organization is deleted, StackJack also deletes every large tool result and every recorded test file it stored for your organization. See Customer data and privacy.

If you withdraw the deletion request while it is waiting, transcript deletions that have not started yet are withdrawn, and any already in progress finish. The automations StackJack switched off while the deletion was waiting are switched back on within a few minutes, and we email the organization's owner the list. An automation someone switched off or deleted in the meantime stays as it is.

Moving your organization to another region

A move to another region cannot start while a transcript deletion is still in progress, or while one could not finish. The files a deletion still has to remove stay in your current region, so the deletion must finish first. Wait until the scheduled deletions finish. If a run's page says its transcript could not be fully deleted, use Try again there or contact StackJack support. Then start the move. See Region migration.

From your AI assistant

A connected AI assistant can do the same with the stackjack_delete_run_transcripts tool, under the same rule: only for an owner or administrator, and never from an automation's own connection. Like the other automation-building tools, the connection needs that tool granted by name. The tool counts first: call it with an empty confirm to get the counts and the exact text to send, then call it again with that text. For every finished run (all: true) the text is DELETE ALL TRANSCRIPTS, and the call deletes every run that has finished by then, including one that finished after the counts. For a list of run ids the text is DELETE <N> TRANSCRIPTS, and if the number changes in between, the call is refused and you ask for the counts again. The automation-building tools take autoDeleteTranscripts to turn the automatic setting on or off. See Platform tools and Building and maintaining automations from your AI assistant.