Issue Summary
Key Definitions:
Registration table - A structured table object in Benchling used to register entities into your registry through a notebook entry. Data submitted through registration tables can be modified by providing a justification of change and resubmitted.
What happened?
Benchling identified an issue which led to missing Notebook entry registration table audit events for Structured Table: Submitted event descriptions, these corresponded to "Created structured table row" or "Updated value" actions in an audit log. This issue only occurred during the time periods listed below. Benchling understands the seriousness of this issue, and wants to clearly state that user-entered data was not lost. Notebook entry versions and registry entity audit logs do capture the entire history of changes made by users.
For non-Validated Cloud Tenants:
- Submit and Update events for all registration table activity between January 8, 2024 and February 13, 2024
- Submit and Update events for registration submissions with <=100 rows, between February 14, 2024 and August 16, 2024
For Validated Cloud Tenants:
- Submit and Update events for all registration table activity between March 22, 2024 and June 14, 2024
- Submit and Update events for registration submissions with <=100 rows, between June 14, 2024 and August 20, 2024
For the time periods where the issue was only applicable to registration tables with <=100 rows, specific conditions that caused each type of impacted audit event to be skipped are listed below:
| Required conditions for missing audit event in registration table audit log during initial table submission | |
| 1 | User populates a registration table, including all required fields for a given schema and has <= 100 rows at the time of submission. |
| 2 | User submits <=100 rows in the registration table |
| Required conditions for missing audit event in registration table audit log upon table re-submission | |
| 1 | User populates a registration table, including all required fields for a given schema and has <= 100 rows at the time of submission. |
| 2 | User submits <=100 rows in the registration table |
| 3 | User updates values in the existing registration table rows or adds additional rows of data |
| 4 | User then resubmits at least one row of data and there are <= 100 rows total in the registration table. |
What happens next?
Benchling is not backfilling the audit log directly. Benchling is able to provide a file with the missing submission events upon request. This file is designed to serve in lieu of the audit trail for the impacted period, and can be used to supplement any deviation record in your QMS, if applicable.
We understand the seriousness of this issue and our team is standing by to support you on this matter. Please reach out support@benchling.com if you have any questions or would like Benchling to provide you with the supplemental file.
FAQs
Does this impact entry or entity audit logs as well?
No, Entity audit logs were not impacted by this issue. All audit events - including the user who performed an update or initial creation, the time stamp of the update or creation, and the update/ metadata values at creation themselves - were not impacted by this issue. Entry audit logs compile table audit log information. No other aspect of entry audit logs, except the registration table audit events noted above, were impacted.
Can Benchling provide me with a list of impacted data?
Please reach out to support@benchling.com if you would like assistance in identifying impacted registration tables.
Does this issue also impact registry data updated in other ways (i.e. in UI or by bulk spreadsheet update?)
No, this does not impact registry or entity data submitted and/or updated in other ways. Audit events were captured for those actions.