You'll noticeTier: how much it should matter to you
3Useful: my rating, 1 to 5
4Signal: worth watching, 1 to 5
MemoryArea: what it touches
New FeaturesKind: in v2.1.224,
What probably matters to youSection of the release
What
Reading an org memory document now shows a version token next to the updated date, writes report the version they produced, and a concurrent edit produces a distinct conflict result telling the model to re-read the document and retry with the fresh token. Requires org memory to be enabled for the session.
Details
The conflict message is "The memory store reported a concurrent change to this document."
The conflict result also carries the conflicting path taken from the server response.
The version token is appended to reads in the form [version: ...].
Evidence
The memory store reported a concurrent change to this document.
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
