# Bug with sorting within a segment **URL:** \ **Category:** Help me!\ **Created:** [March 6, 2025, 4:57pm UTC](https://community.forestadmin.com/t/bug-with-sorting-within-a-segment/7956 "2025-03-06T16:57:11Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![Antonio\_Marino](https://dub1.discourse-cdn.com/flex013/user_avatar/community.forestadmin.com/antonio_marino/32/460_2.png) [@Antonio\_Marino](https://community.forestadmin.com/u/Antonio_Marino)\ **Post date:** [March 6, 2025, 4:57pm UTC](https://community.forestadmin.com/t/bug-with-sorting-within-a-segment/7956/1 "2025-03-06T16:57:11Z")
Hi all, I noticed a new bug that has seemed to been introduced today. When navigating to a segment, the request that ends up being made to the backend (I see it through browser tools) is not including the “sort” query parameter. This is despite the fact that the segment has got sorting configured by a given field and that the same field has got the little arrow up/down indicator in the table headers. ---
**Author:** ![anon62739609](https://avatars.discourse-cdn.com/v4/letter/a/c2a13f/32.png) [@anon62739609](https://community.forestadmin.com/u/anon62739609)\ **Post date:** [March 7, 2025, 9:55am UTC](https://community.forestadmin.com/t/bug-with-sorting-within-a-segment/7956/2 "2025-03-07T09:55:38Z")
Hi @Antonio_Marino, thanks for your report. We’ve made a fix when you reported the issue yesterday, it’s being released right now and should be live in a few minutes 😉 I’ll let you know once it is live ---
**Author:** ![Antonio\_Marino](https://dub1.discourse-cdn.com/flex013/user_avatar/community.forestadmin.com/antonio_marino/32/460_2.png) [@Antonio\_Marino](https://community.forestadmin.com/u/Antonio_Marino)\ **Post date:** [March 7, 2025, 11:25am UTC](https://community.forestadmin.com/t/bug-with-sorting-within-a-segment/7956/3 "2025-03-07T11:25:32Z")
Hi @anon62739609 . Thank you for looking into it quickly. I see the improvement already. I have spotted another bug with segments: when going from a segment A to segment B (segments belonging to different collections!), sometimes it happens that the filters of segment A get carried over in the request made to fetch data for segment B. That often results in either wrongly displayed data or, when column names are completely different, it results in various other errors such as: - An unsupported operator was used, please retry after clearing your filters (directly in the frontend) - 400 from the agent: ValidationError: Invalid filters (The ‘xyzzy’ field was not found. Available fields are: [a,b,c] - 400 from the agent: ValidationError: Invalid filters (The given operator ‘Equal’ is not supported by the column: ‘status’. the column is not filterable) Can this please be looked into? ---
**Author:** ![anon62739609](https://avatars.discourse-cdn.com/v4/letter/a/c2a13f/32.png) [@anon62739609](https://community.forestadmin.com/u/anon62739609)\ **Post date:** [March 7, 2025, 12:53pm UTC](https://community.forestadmin.com/t/bug-with-sorting-within-a-segment/7956/4 "2025-03-07T12:53:14Z")
Okey I do reproduce. I will do a fix quickly. Sorry about that ---
**Author:** ![anon62739609](https://avatars.discourse-cdn.com/v4/letter/a/c2a13f/32.png) [@anon62739609](https://community.forestadmin.com/u/anon62739609)\ **Post date:** [March 7, 2025, 1:54pm UTC](https://community.forestadmin.com/t/bug-with-sorting-within-a-segment/7956/5 "2025-03-07T13:54:52Z")
Hey @Antonio_Marino, The fix should be live. Let me know if your issue is gone 🙏 ---
**Author:** ![Antonio\_Marino](https://dub1.discourse-cdn.com/flex013/user_avatar/community.forestadmin.com/antonio_marino/32/460_2.png) [@Antonio\_Marino](https://community.forestadmin.com/u/Antonio_Marino)\ **Post date:** [March 7, 2025, 2:06pm UTC](https://community.forestadmin.com/t/bug-with-sorting-within-a-segment/7956/6 "2025-03-07T14:06:24Z")
Amazing, thank you! I will keep monitoring the forest agent’s error rates and let you know if it reoccurs.