Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

HTTPClient::SendTimeoutError: execution expired #25

Closed
ResumeNothing opened this issue May 12, 2014 · 2 comments
Closed

HTTPClient::SendTimeoutError: execution expired #25

ResumeNothing opened this issue May 12, 2014 · 2 comments

Comments

@ResumeNothing
Copy link

We've been getting this error while updating Ad Params: HTTPClient::SendTimeoutError: execution expired. For some reason this seems to happen most often between 2am and 4am ET on Mondays and Fridays.

Is it possible to configure send_timeout to be longer? We tried adding it to the connection hash like we did with read_timeout and open_timeout when initializing the API object, but it doesn't seem to have had any effect.

connection: {
  read_timeout: 1800,
  open_timeout: 600,
  send_timeout: 600
}
@nicholaschen
Copy link
Contributor

Hiya,

Apologies, looking at this now, I'm not really 100% sure where you're setting this (or in what context you're trying to extend the timeout for sending a request). Not sure if this is still an issue, but let us know and we'll take a look.

@ResumeNothing
Copy link
Author

I don't think we're having this issue anymore, but thanks for following up!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants