4

Problem:I am calling URLFetch with a deadline of 480 seconds from within a TaskQueue, but it is timing out after only 60 seconds.

The original question was asked in official group more than year ago, but still unanswered.

Bug confirmed, but there is no technical support or developers of gae. Maybe they're here?

user1702903
  • 53
  • 4

1 Answers1

3

While there is information on this old thread that suggests otherwise, I don't believe this is a bug that will be fixed (or that it is a bug). It's unfortunate that this issue has not been updated or closed.

A Urlfetch (regardless) of where you make it from within appengine world has a maximum deadline of 60 seconds.

Requests on front end instances within appengine also have a lifetime of a maximum of 60 seconds.

Requests within the context of the Taskqueue however, have a lifetime of up to 10 minutes. This however does not mean that you can make a Urlfetch made from within the taskqueue context exceed the 60 second deadline.

Jesse
  • 7,773
  • 5
  • 43
  • 71
  • 2
    if that it is not a bug - then reasonable raise an exception when trying to set the timeout more than 60 seconds, regardless of the context. Need to fix documentation. This behavior confuses people. – user1702903 Apr 26 '15 at 08:21
  • 2
    I agree, I wish that Google was better at cleaning up / maintaining there public issue tracker. – Jesse Apr 26 '15 at 14:36