Note that there are some explanatory texts on larger screens.

plurals
  1. POIf Google App Engine cron jobs have a 10 minute limit, then why do I get a DeadlineExceededError after the normal 30 seconds?
    primarykey
    data
    text
    <p>According to <a href="https://developers.google.com/appengine/docs/python/config/cron" rel="nofollow">https://developers.google.com/appengine/docs/python/config/cron</a> cron jobs can run for 10 minutes. However, when I try and test it by going to the url for the cron job when signed in as an admin, it times out with a DeadlineExceededError. Best I can tell this happens about 30 seconds in, which is the non-cron limit for requests. Do I need to do something special to test it with the cron rules versus the normal limits?</p> <p>Here's what I'm doing:</p> <ul> <li>Going to the url for the cron job</li> <li>This calls my handler which calls a single function in my py script</li> <li>This function does a database call to google's cloud sql and loops through the resulting rows, calling a function on each row that use's ebay's api to get some data</li> <li>The data from the ebay api call is stored in an array to all be written back to the database after all the calls are done.</li> <li>Once the loop is done, it writes the data to the database and returns back to the handler</li> <li>The handler prints a done message</li> </ul> <p>It always has issues during the looping ebay api calls. It's something like 500 api calls that have to be made in the loop.</p> <p>Any idea why I'm not getting the full 10 minutes for this?</p> <p>Edit: I can post actual code if you think it would help, but I'm assuming it's a process that I'm doing wrong, rather than an error in the code since it works just fine if I limit the query to about 60 api calls.</p>
    singulars
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload