Error with Sendlane contact_history endpoint


The user is encountering a ‘source is unresponsive’ error for the contact_history endpoint in Sendlane. The error message indicates a heartbeat timeout issue.


Hey guys. I am getting a source is unresponsive error for contact_history endpoint for Sendlane. Could someone tell me what could go wrong?

  "failureOrigin" : "source",
  "failureType" : "heartbeat_timeout",
  "internalMessage" : "Heartbeat has stopped. Heartbeat freshness threshold: 3600 secs Actual heartbeat age: 3610 secs",
  "externalMessage" : "The source is unresponsive",
  "metadata" : {
    "attemptNumber" : 4,
    "jobId" : 493,
    "connector_command" : "read"



This topic has been created from a Slack thread to give it more visibility.
It will be on Read-Only mode here. [Click here]( if you want to access the original thread.

[Join the conversation on Slack](

["source-is-unresponsive", "contact-history", "sendlane", "heartbeat-timeout"]

The “source is unresponsive” error typically occurs when the source connector doesn’t send any data or heartbeat signal for a certain period of time. In your case, the heartbeat freshness threshold is 3600 seconds (1 hour), and the actual heartbeat age is 3610 seconds. This means that the source connector didn’t send any data or heartbeat signal for 3610 seconds, which exceeded the threshold, hence the error. This could be due to a variety of reasons such as network issues, the source API not responding, or the source connector taking too long to fetch the data. Unfortunately, the provided extracts do not contain specific information about the Sendlane connector or the contact_history endpoint. Therefore, I would recommend checking the following: 1. Network connectivity: Ensure that your network connection is stable and you are able to reach the Sendlane API from your machine. 2. API response: Test the Sendlane API endpoint directly (outside of Airbyte) to see if it’s responding as expected. 3. Connector configuration: Review your Sendlane connector configuration in Airbyte to ensure it’s set up correctly. 4. Logs: Check the detailed logs in Airbyte for any additional error messages or clues. If the issue persists, you might want to reach out to the Airbyte community on Slack or Discussions for further assistance.