The maximum ETA allowed is "30 days from the current date and time".
See here: https://cloud.google.com/appengine/docs/java/taskqueue/overview-push?hl=it#Java_Quotas_and_limits_for_push_queues >From our experience, the push queues do an excellent job of living up to their promise of running each task at least once (with an execution time pretty much spot on to the desired time), no matter how far out the ETA is. Apart from that, I'd advise that whatever your task plans on doing, it should check to ensure that its work is still relevant. E.g. if you're scheduling a task to run in 24 hours which emails a new user reminding them to verify their email address, you should ensure that their email address is still unverified at the start of the task execution. Nick On 20 December 2014 at 07:20, Andrew Greene <[email protected]> wrote: > Are there any risks/cautions around creating tasks in a push queue with an > ETA of say 1 month or 1 year or even longer from now? > > Thanks, > Andrew > > -- > You received this message because you are subscribed to the Google Groups > "Google App Engine" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > Visit this group at http://groups.google.com/group/google-appengine. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/google-appengine. For more options, visit https://groups.google.com/d/optout.
