Hey there @angel.mendoza@daveramsey.com,

To get some clarity on what could be going wrong, I’d like to open with a few questions.

Do you happen to have a retry mechanism in place for your setup? If you happen to get a 500 error when attempting a connection, what steps do you take to retry the call at any given time increment? Sometimes its something that could happen with any app’s api from Facebook to Google to Hubspot but wise approach is to sleep for a 1 second or so and retry the call that failed.

Let us know any updates!

Alex

Hi Alex

I do have a retry mechanism in place. It’s implemented with an exponential backoff algorithm.

I do not get a 500. Right when I attempt to make the http call, my program throws an IOException due to the error at a lower layer in the network stack. Essentially, the connection got terminated by the remote host (klaviyo)

The Http connection gets created on the retry which is why this is not a big deal. I am looking for guidance from you guys as to how long will it take your host to kill my HTTP2 connection so I can tune my http client configuration

Thanks for the info @angel.mendoza@daveramsey.com,

I think we might need a few more details to understand what might be going on. 

1. What did you try to call exactly and what are you getting?
2. Is this a timeout?

Thanks for the cooperation!

Alex

1. Klaviyo’s Track API
2. It’s not a request time out.  It’s not a connection timeout. Apparently, it’s the remote host (Klaviyo) saying the HTTP2 connection has lived for too long and it terminates it

Hey @angel.mendoza@daveramsey.com,

I think it would be really helpful if you can provide an example call of the Track API you are making that gets terminated. Remember to hide any sensitive data such as your Klaviyo IDs, etc. 

If you are uncomfortable sharing this information sometimes it may be more appropriate reaching out to our support channels who can assist you further in seeing the types of calls you are making specific to your account. 

David