Failed DB graph download leaves an empty local graph that blocks clean retry

Search first

• I searched open and closed issues. The iOS empty-graph report is a different successful-import and persistence case.

What happened?

A failed DB graph snapshot download leaves a canonical local graph database behind. Desktop can then open that empty graph, and the CLI can reject a later correct retry because the graph already exists.

This reproduced through multiple pre-import failures:

• Missing E2EE password.
• Incorrect E2EE password.
• TLS failure during the initial :fetch-pull request.
• db-worker runtime startup failure.

The remote snapshot was never imported, but <root>/graphs/<graph> remained. In Desktop, selecting or restoring that graph showed an empty journal and no remote pages. If it remained the startup graph, relaunching opened or recreated the empty graph without initiating a new remote download.

Manual recovery required switching to another graph, removing the failed local graph, and retrying the remote download.

Reproduce

1. Choose a remote DB graph that does not exist locally.
2. Force a failure before snapshot import, for example an incorrect E2EE password or unreachable sync endpoint.
3. Observe the download error.
4. List or open local graphs.
5. Retry with valid credentials or connectivity.

Expected behavior

Snapshot download should be transactional. Preparation should occur in temporary storage, and a new local graph should be promoted only after successful import. A failed newly-created database should be removed automatically or clearly marked as an incomplete download that can be retried.

Platform

• Logseq Desktop 2.0.1 on macOS arm64
• Current CLI repository build
• DB Sync, including E2EE graphs

Start at the DB graph snapshot download and pre-import setup described in the reproduction steps, then trace when the canonical local graph is created and when import succeeds or fails. Reproduce a pre-import failure with incorrect credentials or an unreachable endpoint; done means failed new downloads leave no usable empty graph and a valid retry can proceed cleanly.