Skip to content

Free, Open Source, Self-Hosted WhatsApp API Gateway

docs(api): note that an aborted storage import keeps its writes

Yudhi Armyndharisfbff410ad8c1
diff --git a/docs/06-api-specification.md b/docs/06-api-specification.md
index 44d97d79f..80c0d13ec 100644
--- a/docs/06-api-specification.md
+++ b/docs/06-api-specification.md
@@ -5887,7 +5887,7 @@ Import storage files from a `tar.gz` located inside the `data/` directory.
`failed` counts archive entries the store refused to write; a bad or traversing entry is skipped without failing the rest. `imported` is `false` when entries failed and none was written.
-**Errors:** `400` missing/out-of-`data/`/not-found path, or `Storage import failed: <reason>` when the file is not a readable gzip tar archive or exceeds the import resource caps · `401` · `403` · `500` · `503` S3 configured but not reachable since boot (a later outage answers `200` with `imported: false` and the entries in `failed`)
+**Errors:** `400` missing/out-of-`data/`/not-found path, or `Storage import failed: <reason>` when the file is not a readable gzip tar archive or exceeds the import resource caps (an abort keeps the entries written before it, since there is no rollback; re-run the import once the archive is fixed, as each entry overwrites) · `401` · `403` · `500` · `503` S3 configured but not reachable since boot (a later outage answers `200` with `imported: false` and the entries in `failed`)
---