Page properties no longer visible (appear blank) but exist on synced devices

Nobody has claimed this yet.

### Search first

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

### What Happened?

A #Person tag is gradually populated via journal entries (kind of CRM functionality). For each entry, additional properties can be set at a later stage (e.g. First Name, Surname, Organisation, etc.). After these additional properties have been added, these tend to 'disappear' after some time: gone from the Table View and also gone from the entry's page view.
However, when checking on a synced device, the additional properties are still visible _(i.e. that suggests a front-end binding issue)_.
The issue is experienced regularly on the Windows version (and only once on the web version). Have not experienced this on iOS version. The iOS version has always shown the property values once populated _(but iOS is less convenient to work with, so not used as extensive for entry)_

### Reproduce the Bug

1. Open the #Person page in table view
2. Open a couple of times a page for one of the entries from the table view
3. After some time, some of the properties in the table view go blank (incl. 'Created At' and 'Updated At' fields)
4. Open the page for an entry with 'missing' properties; the properties on that entry page are now also missing
5. When opening a synced device, the properties are still visible
6. Application restart does not resolve the issue

### Expected Behavior

Properties should not spontaneously disappear

### Screenshots

Showing #Person page in List View. **Windows Version** versus synced **Browser Version** next to each other to proof that property values still exist (but not shown on Windows version). In the bottom, the page view of entry with 'invisible' properties showing these are also invisible in that view.
_(N.B. some populated fields blurred for privacy reasons)_

### Files

_No response_

### Browser, Desktop or Mobile Platform Information

Logseq-win-x64-2.0.1 issued 13-JUL-2026

### Additional Context

_No response_

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

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

No files or tests are identified. Start by reproducing the issue in Logseq-win-x64-2.0.1 using the listed table and page-view steps, then compare the Windows view with a synced browser device to determine where the property values stop being displayed. Done means the properties remain visible after repeated page navigation and synchronization.

Written by the indexing model from the issue text.