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 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:
- Change the Export Mode (
Full history/From setup date/From custom date). Changing the mode resets the sync position so the new mode's start-date logic takes effect — for example, switching toFull historyre-scans from the earliest data. Editing other fields does not reset this. - 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 the full list of status badges and what they mean, see Export status.
Last edited
