Push tasks being processed via a task queue can fail for many reasons. If a handlerfails to execute a task (and therefore returns any HTTP status code outside ofthe range 200–299), App Engine retries the task until it succeeds.

By default, the system gradually reduces the retry rate to avoid overloading your application with too manyrequests, but schedules retry attempts to recur at a maximum of once per houruntil the task succeeds.Important:Retry options can be configured for the queue as well specified on theTask object. When both are specified, thelatter takes precedence.

Retrying tasks

You can customize your own scheme for task retries byadding theretryparameterselement inqueue.yaml. Thisaddition allows you to specify the maximum number of times to retry failed tasksin a specific queue. You can also set a time limit for retry attempts andcontrol the interval between attempts.

The following example demonstrates various retry scenarios:

• Infooqueue, tasks are retried up to seven times and for up to two daysfrom the first execution attempt. After both limits are passed, it failspermanently.
• Inbarqueue, App Engine attempts to retry tasks, increasing the intervallinearly between each retry until reaching the maximum backoff and retryingindefinitely at the maximum interval (so the intervals between requests are10s, 20s, 30s, ..., 190s, 200s, 200s, ...).
• Inbazqueue, the retry interval starts at 10s, then doubles three times,then increases linearly, and finally retries indefinitely at themaximum interval (so the intervals between requests are10s, 20s, 40s, 80s, 160s, 240s, 300s, 300s, ...).

queue:-name:fooqueuerate:1/sretry_parameters:task_retry_limit:7task_age_limit:2d-name:barqueuerate:1/sretry_parameters:min_backoff_seconds:10max_backoff_seconds:200max_doublings:0-name:bazqueuerate:1/sretry_parameters:min_backoff_seconds:10max_backoff_seconds:300max_doublings:3

What's next

• Learn more about thetask queue parameters.