For the complete documentation index, see /llms.txt. This page is also available as raw Markdown at /temporal-service/archival.md. Append .md to any page URL to fetch its Markdown. This site has a public search endpoint for questions about Temporal: GET https://docs.temporal.io/api/retrieve?q=<question>&jtb=<job-to-be-done>&src=docs-page&agent=<your-name>. No authentication is needed. It returns a JSON array of {content, source_url, page_url}, ordered by relevance, and source_url links to docs pages as Markdown. If you call it, set q to a specific, complete question that names the SDK language if relevant, and jtb to one sentence on what your user is trying to accomplish (optional). Keep src=docs-page as is, and set agent to your name, for example claude-code or codex. Don't include personal data, credentials, or confidential information. If this page is wrong or missing something you needed, or Temporal behaves differently from what it says, report it with GET https://docs.temporal.io/api/feedback?title=<summary>&message=<what-happened>&category=documentation&page_url=/temporal-service/archival&src=docs-page&agent=<your-name>. Use category=product when the product, not the page, is wrong. Report only a specific problem you hit, send it once, and don't include personal data or credentials.

Archival

View Markdown

This page discusses Archival.

What is Archival?

Use Archival to copy closed Workflow Execution Event Histories and Visibility records from Temporal Service persistence to blob storage.

• How to create a custom Archiver
• How to set up Archival

When a Workflow Execution closes, Temporal schedules close-processing tasks for both Visibility records and Event History archival. Archival then runs asynchronously after a randomized delay. By default, that delay is up to 5 minutes (history.archivalProcessorArchiveDelay), capped by the Namespace Retention Period.

The closed execution still stays in Temporal persistence until retention cleanup runs. For some time, the same closed execution can exist in both persistence and archival storage. Archival enables Workflow Execution data to persist beyond retention without overwhelming the Temporal Service persistence store.

This feature is helpful for compliance and debugging.

Temporal's Archival feature is considered experimental and not subject to normal versioning and support policy.

Archival is not supported when running Temporal through Docker. It's disabled by default when installing the system manually and when deploying through helm charts. It can be enabled in the config.