---
title: I changed my blob storage config — why didn't it re-export, and why do I still see an error?
seoTitle: "Blob Storage Config Changes and Export Errors"
description: How configuration changes apply to a Langfuse blob storage export, why a fixed misconfiguration can still show an error, and how to re-export historic data.
tags: [platform, integration]
---

# I changed my blob storage config — why didn't it re-export, and why do I still see an error?

Two behaviors of the [blob storage integration](/docs/api-and-data-platform/features/export-to-blob-storage) commonly cause confusion after you edit a configuration: changes apply only to future exports, and a fixed error keeps showing until the next successful run.

Editing an integration (credentials, bucket, prefix, frequency, file type, export source, field groups, or compression) applies to **future exports only**. It does not re-export data that was already exported (or skipped) under the previous configuration; the export continues from where it left off.

There are two ways to re-export historic data:

1. **Change Export Mode** (`Full history` / `From setup date` / `From custom date`). Changing this setting resets the sync position so the selected start date takes effect. For example, switching to `Full history` re-scans from the earliest data. Editing other fields does not reset this.
2. **Reset the integration.** The **Reset** button removes the integration; you then reconfigure it from scratch and it starts fresh.

**Run Now** triggers an immediate export of data **since the last sync**; it does not re-export history.

  The **Error** state is sticky: fixing a misconfiguration (for example, wrong credentials) does not immediately clear the Error badge or the "Last export failed" alert. The recorded error is cleared only when an export next succeeds. Use the **Validate** button to confirm a new configuration works without waiting for the next scheduled run.

For export delays, backfills, and retry behavior, see [How do blob storage export timing and retries work?](/faq/all/blob-storage-export-timing-and-retries).

<!-- 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-config-changes-and-errors.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>.