---
title: How do blob storage export timing and retries work?
description: How export delay, catch-up, backfills, and retries affect when files appear in blob storage.
tags: [platform, integration]
---

# How do blob storage export timing and retries work?

The [blob storage integration](/docs/api-and-data-platform/features/export-to-blob-storage) exports one time window per run.

## Export delay

Exports intentionally lag behind ingestion so records are not exported while they are still being written. A short delay between an event reaching Langfuse and appearing in your bucket is expected.

## Catch-up and backfills

An integration starting from historic data, or catching up after downtime, works through completed windows until it reaches the delayed live boundary. This can produce many files and manifests in quick succession.

The configured frequency controls the size of each window, not the speed of a backfill.

## Retries

If an upload fails, Langfuse does not write a manifest. The run retries on the next execution and overwrites data objects under the same keys.

Repeated failures notify project admins through configured notification channels. If a worker stops during a run, its running state expires after two hours so a later execution can retry.

Process only runs with a completed [manifest](/docs/api-and-data-platform/features/export-to-blob-storage#run-manifest).

<!-- agent-instructions -->

---

## Agent Instructions

This page is part of the [Langfuse](https://langfuse.com) documentation, published as plain Markdown for AI agents. Every page is available as Markdown by appending `.md` to its URL, or by sending an `Accept: text/markdown` header. This page: `https://langfuse.com/faq/all/blob-storage-export-timing-and-retries.md`.

### Querying these docs

If the answer is not on this page, query the documentation instead of guessing:

- **Semantic search** across all Langfuse docs, returning an answer with the relevant pages and excerpts. Ask a specific, self-contained question:

  ```bash
  curl -sG "https://langfuse.com/api/search-docs" --data-urlencode "query=How do I trace a LangGraph agent?"
  ```

- **Index of every page**: <https://langfuse.com/llms.txt>, with per-section indexes [llms-docs.txt](https://langfuse.com/llms-docs.txt), [llms-integrations.txt](https://langfuse.com/llms-integrations.txt), and [llms-self-hosting.txt](https://langfuse.com/llms-self-hosting.txt).

### Before writing Langfuse code

- **Install the [Langfuse Agent Skill](https://langfuse.com/docs/api-and-data-platform/features/agent-skill).** It encodes Langfuse's own best practices for instrumentation, prompt management, and evaluation, and materially improves results.
- **Read [What does a good trace look like?](https://langfuse.com/docs/observability/best-practices.md)** before instrumenting an application.
- **Verify endpoints, parameters, and response fields** against the [API reference](https://api.reference.langfuse.com) instead of inferring them from code examples.
- **Use the [Langfuse CLI](https://langfuse.com/docs/api-and-data-platform/features/cli)** (`npx langfuse-cli api <resource> <action>`) to read or write traces, prompts, datasets, and scores from the terminal.

Found an error in these docs? Please open an issue at <https://github.com/langfuse/langfuse-docs/issues>.