Wrong sorting for duplicated Objects

WHAT IS THE BUG
When an Object becomes duplicated, it appears at the bottom of a Grid View, instead on top.

HOW TO REPRODUCE IT

  1. Take a Grid View that’s sorted for “Last modified date”, in descending order.
  2. Duplicate one of the Objects there.
    → The duplicate appears on the bottom of the Grid.

That’s wrong – it should appear on top position.
And that’s annoying, because it forces the user to “endless” scroll down so that he can open and edit the new Object.

THE EXPECTED BEHAVIOR
Like a normal new generated Object, also a duplicated (and therefore new generated) Object should appear on top of a Grid that’s sorted for “Last modified date” in descending order.

ADDITIONAL CONTEXT
I see this wrong behavior again and again on different places of the App: a new created Object (duplication is a new creation) MUST get the Property “Last modified date” of NOW (exactly this moment)!
But Anytype “forgets” to set the Property value correct. It sets only the Value of the Property “Creation date”, but it forgets to also set “Last modified date”.

TECHNICAL INFORMATION
OS version: win32 x64 10.0.19045
App version: 0.55.5
Build number: build on 2026-06-02 16:45:57 +0000 UTC at #5e888f1b9b8590575ea81da218e95c472daf0fdf
Library version: v0.50.8
Anytype Identity: AAtt6aReARByswg2CbvZhveoJEEcnydfDu7U2VAkgJALsE7D
Analytics ID: 8a514008-4f5d-40d3-970f-a0d241b63af2
Device ID: 12D3KooWAJep6PSzKnkLhrTv11sfv6hQJZw18UfqsQDX6QdNNit1
Ethereum Address: 0x2da4881c5D6689bac7d6B6BC00D8862aACca9B60

Yes, I marked this one in our logs.