[GH-ISSUE #8575] [Bug] sorting criteria not always working as intended #3921

New issue

Open

opened 2026-03-23 21:34:09 +00:00 by mirror · 0 comments

mirror commented

2026-03-23 21:34:09 +00:00

Owner

Originally created by @Ray0m on GitHub (Mar 13, 2026).
Original GitHub issue: https://github.com/AppFlowy-IO/AppFlowy/issues/8575

Originally assigned to: @appflowy on GitHub.

Bug Description

I have noticed multiple strange issues with sorting that might be intersecting with other issues making hard to isolate precisely why sorting isn't always working.
In this video, a sorting property is not working and can be analysed : https://www.youtube.com/watch?v=BwcVOjSKIBo&t=510s
That said, I am unclear if the issue is with sorting itself or due to other issues such as general latency / slow performance of appflowy in general when dealing with big databases, or also it could be related to what kind of property is being used for sorting; like, perhaps relational data for sorting misbehaves more often? hard to tell. again, please watch video.

How to Reproduce

use a large DB with many entries and property types
apply multiple sorting criteria to sort all of your data
take any of your sorted data and change one of the datapoints currently being used for sorting
(so for exemple, if you are currently sorting by date, change the date on one of or multiple entries on which the sorting is being applied - notice how that entry should now "move" to it's new location in the sorting and yet, in many cases you will observe the following problems :
a. changed entry not going where it should be sorted according to criteria (in the wrong place, or no longer in list at all)
b. changed entry taking a very long time to update it's placement in the sorting
repeat step 3 by changing data points of other properties you are also sorting by to find out if different property types are more likely to have problems. (so if my original exemple at 3 was "sort by date", now add a second sort by another property type like a number or text field, and repeat step 3 (change data points of some of the pages and notice again issues a. and b. written above).

The worse issue i have is sometime some data is plainly missing once I apply a sort. That is very strange indeed (again see video)

It also seems that sorting is particularly broken when using grouping function.
IF you group DB and then follow all of the above steps, I believe data is much more likely to have problems.

Expected Behavior

any data changes to properties currently being used for sorting should change their sorting order simply and quickly.

Operating System

windows 11

AppFlowy Version(s)

0.11.4

Screenshots

No response

Additional Context

No response

Originally created by @Ray0m on GitHub (Mar 13, 2026). Original GitHub issue: https://github.com/AppFlowy-IO/AppFlowy/issues/8575 Originally assigned to: @appflowy on GitHub. ### Bug Description I have noticed multiple strange issues with sorting that might be intersecting with other issues making hard to isolate precisely why sorting isn't always working. In this video, a sorting property is not working and can be analysed : https://www.youtube.com/watch?v=BwcVOjSKIBo&t=510s That said, I am unclear if the issue is with sorting itself or due to other issues such as general latency / slow performance of appflowy in general when dealing with big databases, or also it could be related to what kind of property is being used for sorting; like, perhaps relational data for sorting misbehaves more often? hard to tell. again, please watch video. ### How to Reproduce 1. use a large DB with many entries and property types 2. apply multiple sorting criteria to sort all of your data 3. take any of your sorted data and change one of the datapoints currently being used for sorting (so for exemple, if you are currently sorting by date, change the date on one of or multiple entries on which the sorting is being applied - notice how that entry should now "move" to it's new location in the sorting and yet, in many cases you will observe the following problems : a. changed entry not going where it should be sorted according to criteria (in the wrong place, or no longer in list at all) b. changed entry taking a very long time to update it's placement in the sorting 4. repeat step 3 by changing data points of other properties you are also sorting by to find out if different property types are more likely to have problems. (so if my original exemple at 3 was "sort by date", now add a second sort by another property type like a number or text field, and repeat step 3 (change data points of some of the pages and notice again issues a. and b. written above). The worse issue i have is sometime some data is plainly missing once I apply a sort. That is very strange indeed (again see video) It also seems that sorting is particularly broken when using grouping function. IF you group DB and then follow all of the above steps, I believe data is much more likely to have problems. ### Expected Behavior any data changes to properties currently being used for sorting should change their sorting order simply and quickly. ### Operating System windows 11 ### AppFlowy Version(s) 0.11.4 ### Screenshots _No response_ ### Additional Context _No response_