I observed an issue while creating and updating Package entities through multiple threads. The createUpdateTime field retains the original creation timestamp even after the entity is updated.
As a result, the system cannot detect the latest updated entities, which is causing problems in scenarios where recent updates need to be fetched or processed.
Below are sample logs for reference:
Created entity information: internal id: {6A07B956-9480-49f8-B152-0CC037663F4C}, createUpdateTime: Fri Oct 17 07:50:24 IST 2025 [1760667624000]
Created entity information: internal id: {09BAF529-F7F5-47a3-BE5C-895CED4368AB}, createUpdateTime: Fri Oct 17 07:50:27 IST 2025 [1760667627000]
Created entity information: internal id: {2A2FE9A1-8F42-4877-9467-2F813E335A44}, createUpdateTime: Fri Oct 17 07:51:03 IST 2025 [1760667663000]
Created entity information: internal id: {AEFBBB2B-10E5-4106-87B8-B03AB8144657}, createUpdateTime: Fri Oct 17 07:51:07 IST 2025 [1760667667000]
Updated entity information: internal id: {6A07B956-9480-49f8-B152-0CC037663F4C}, createUpdateTime: Fri Oct 17 07:50:24 IST 2025 [1760667624000]
Updated entity information: internal id: {09BAF529-F7F5-47a3-BE5C-895CED4368AB}, createUpdateTime: Fri Oct 17 07:50:28 IST 2025 [1760667628000]
Steps to Reproduce:
Create four Package entities using Thread 1.
Update the first two entities using Thread 2.
Check the createUpdateTime in the update logs or response.
The field should reflect the last updated timestamp after modification, or there should be another field (e.g., lastModifiedTime) indicating the latest update time.
Is createUpdateTime intended to represent creation time only, or should it update upon modification?
Could this be a concurrency issue between threads updating entities simultaneously?
Is there a dedicated field for tracking the last modified time?
Could this be caused by caching or delayed persistence?
What is the recommended approach or workaround to retrieve the actual last updated time of an entity?
Due to this behavior, it is not possible to accurately determine which entities were recently modified.
This leads to missed updates and inconsistent data during sync or polling operations.
