Key Definitions:
- modified_at Timestamp: A system-generated timestamp that records the last time a task or object was modified. This is not directly entered by the user but is automatically updated by the system. This is distinct from the audit log, which tracks detailed changes to an object.
- Snapshot Fields: Fields within a task that store a snapshot of specific data at a point in time. These are typically recalculated during task execution or completion.
What happened?
Benchling identified an issue where tasks had an unexplained modified_at timestamp. Investigation revealed that the issue was triggered by the addition of some snapshot field value metadata in the database, which led to the modified_at timestamp being updated without corresponding changes being logged in the audit log. The snapshot fields themselves were not recalculated, but the metadata update resulted in the erroneous modified_at updates.
Impacted Data and Conditions
- Workflows Tasks: The primary objects affected were tasks within the Workflows application. These tasks had their modified_at timestamps updated incorrectly due to the snapshot recalculations.
- Other Schematized Objects: While the primary focus has been on workflow tasks, further investigation revealed results and workflow outputs were also impacted
What does this mean for you?
For tenants operating in non-GxP environments, this issue primarily affected tasks and other objects between February 2023 and August 30, 2024.
For validated/GxP tenants, the impact has been identified in results, but not in workflow tasks or outputs. While our primary focus has been on non-GxP environments, we are carefully reviewing the situation to ensure data integrity across all environments.
Affected tasks and objects may show a modified_at timestamp that does not correspond with the last audit log entry. This discrepancy does not indicate data corruption, but it could complicate audit trails.
What happens next?
Benchling has implemented a fix to prevent further discrepancies with the modified_at timestamps. This solution ensures that future updates do not inadvertently change the modified_at timestamps in other areas where it could potentially occur.
- The fix has been applied across all GxP and non-GxP tenants.
Benchling is coordinating with affected clients to ensure a smooth resolution process.
FAQs
Does this impact my data in any way?
While the modified_at timestamps were updated in select circumstances, there is no evidence of data corruption and data directly added by users remains unaffected.
Can Benchling provide me with a list of impacted data?
Yes, Benchling can provide a list of impacted tasks and objects. Please contact support@benchling.com if you require this information.
Does this issue appear when updating data in structured tables?
This issue impacts results, which can appear within structured tables. However, it does not directly affect the structured tables themselves.