Open WebUI community reports document edits out of sync: RAG sees new content, but downloads may still return the old file

Open WebUI’s document management has a consistency issue worth noting for RAG deployments. Issue #31912, filed on October 4, reports that in a Docker deployment running 0.11.4, editing text through the document content update endpoint updates the database and vector search results, while downloading the file still returns the original text from upload. As of this review, the issue remains open and lists no related fix. Community report

The reporter’s steps were to upload a text file containing Hello World, then call POST /api/v1/files/{id}/data/content/update to change its contents. According to the report, file.data.content was updated and RAG search returned the new text, but GET /api/v1/files/{id}/content and the file on disk still contained the old text. This case points to a discrepancy between storage layers for the same document. The current evidence comes from the submitter, so it does not establish that all storage backends are affected. Reproduction steps

The official maintenance documentation confirms that Open WebUI stores the database, uploaded files, and vector data separately. Copying only webui.db does not include the files themselves, and local vector storage has its own directory; when an external vector database is used, vectors are stored in that external service. This documentation supports the architectural context of multiple storage layers, but does not confirm this specific bug. Data migration guide

The technical risk is that seeing new text in model retrieval alone does not verify that a document update completed successfully across all storage layers. If the report is accurate, retrieval results and the downloaded version of the same document may differ; backing up only the uploads directory may also fail to preserve the edited text. This does not mean that a complete backup will necessarily fail: the official update guide says backups should include the Docker data volumes for both the database and uploaded files. Backup and restore guide

Engineering teams can follow the reported steps to compare the edited database content, retrieved passages, and downloaded file, and verify version consistency during restore drills. Going forward, watch for how maintainers define the relationship between the originally uploaded file and editable text, and whether they provide a synchronization fix or a clear API contract. Until then, treat this as a community report with reproduction steps; its scope and the version containing a fix remain unconfirmed.