logseq / logseq/db-test

Graph stuck in "Preparing" state forever

Open
#890 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
No language data
Stars
28
Forks
2
PR merge metrics
No merged PRs in 30d

Description

### Search first

- [x] I searched and no similar issues were found

### What Happened?

I have one graph called "oeioeioi" that shows "Preparing" in the list. When i click on it, nothing happens. The graph is not opened.

When i click on it from the **All graphs** view under "Remote graphs", it is opened. It does not show the sync status icon! So i guess sync also does nothing.

It seem to be valid:

> Your graph is valid! {:entities 197, :pages 141, :blocks 42, :classes 18, :properties 113, :objects 10, :property-pairs 611, :datoms 2402}

It has basically no content. 6 blocks in 2 journal pages with 3 characters each like "oei".

### Reproduce the Bug

I'm not able to reproduce it. And i'm also not sure how this happened.

Maybe it happened when i enabled "Use Logseq Sync?" from the "Create a new graph" dialog.

### Expected Behavior

No issues with graphs. It should never happen that a graph is stuck between offline and online graph.

### Screenshots

Image

Image

### Files

_No response_

### Browser, Desktop or Mobile Platform Information

Logseq Linux Binary 2.0.1-alpha+nightly.20260520
NixOS 25.11.10684.8fd9daa3db09

### Additional Context

This sounds similar: https://github.com/logseq/db-test/issues/846

#### Workaround

If this happens to you with a real production graph, you can use this workaround:

1. Export graph
2. Import graph
3. Enable Sync

### Are you willing to submit a PR? If you know how to fix the bug.

- [ ] I'm willing to submit a PR (Thank you!)

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by comparing this report with db-test issue 846 and investigate how the affected graph moves between offline and online states during Sync setup. Reproduce the stuck “Preparing” state if possible, then verify that the graph opens and its sync status is handled consistently without requiring export and re-import.

Written by the indexing model from the issue text.

Assessment

Domain
database
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.