Tetra Benchling Connector Troubleshooting Guide
The following are potential issues you can encounter when using the Tetra Benchling Connector and suggested actions that you can take to resolve them.
Troubleshoot Error Messages
Error messages display on the Connector’s Connector Details page in the Tetra Data Platform (TDP). The Tetra Benchling Connector can return errors if it wasn't configured correctly or if operational errors (such as network issues) occur while the Connector is running.
To access the Connector Details page, see Review and Edit a pluggable Connector’s Information.

Tetra Benchling Connector Error Example
Error Codes and Recommended Actions
The following are errors that the Tetra Benchling Connector can return, the potential issues that can cause them, and recommended actions for resolving each error.
Error Code | Error Message | Potential Issues | Recommended Actions |
---|---|---|---|
| The connector does not have permission to access the SQS queue. Please check your connector and AWS configurations and try again. |
|
|
| SQS Queue not found. Please check your connector and AWS configurations and try again. |
|
|
| The resource for an event in Benchling was not found or the connector does not have permission to access it. If the error does not resolve, manual remediation will be required. | Missing or incorrect project permissions in the Benchling App | Make sure that the Benchling App has read access to the projects and schemas where events are created. You can configure permissions by either adding the app directly to the project, or through inherited permissions from a specific Benchling organization or team. For more information, see Adding apps to projects in the Benchling documentation. |
| Failed to authenticate. Please check your Benchling credentials and try again. |
|
|
| Exceeded Benchling API rate limit. The event will automatically be reprocessed. If the error does not resolve, manual remediation will be required. |
|
|
| Unknown error encountered. Please check logs for more details. | An unknown error occurred |
|
Troubleshoot Missing Files
The following are potential reasons why files either are missing, or might appear to be missing in the TDP.
Potential Issue | Recommended Action |
---|---|
The events aren’t in the Benchling subscription | When you create a Benchling subscription as part of setting up the Connector, make sure that you select all of the required event types for the resources you want available in the TDP. |
Benchling experienced a service outage in their events delivery system | Because events haven’t been to delivered to the TDP from Benchling, customers are responsible for manual remediation by doing the following: Benchling will provide the service outage window. Using the outage window time frame, query all events from the Benchling Events API, group the affected events into batches, and then organize them by resource type and schema ID. For each distinct Benchling resource, a RAW file must be constructed by retrieving the resource from the event’s API URL. These should then be uploaded to the TDP either manually or by using the File Upload API. |
Activity in Benchling didn’t create an event | Not all activity in Benchling creates the expected event. For example, edits to the Notes of an Entry don't generate events. Similarly, uploading assay results to Benchling doesn't generate events. For more information, see the Benchling Events Reference. |
Events expired because of the Amazon SQS queue’s retention policy | When the Tetra Benchling Connector is deactivated or idle longer than the retention period for the Amazon SQS queue, events can be missed and are no longer retrievable. The default retention period is 14 days. |
Updated 5 days ago