IssueTracker

I am not sure what the "7 day lock period" is that is referenced in the original post. But a way to either remove or change the eta of a named task would be very useful.

[Comment deleted]

There's some crossover with this issue as well - http://code.google.com/p/googleappengine/issues/detail?id=1774

It would definitely be useful to have some way to see what named tasks have already been queued.  There are sometimes background house-keeping tasks that you want to schedule in response to some user action, but you don't want the house-keeping to occur multiple times.  For instance:

User A takes Action X -> Schedule task T1 to occur in 10 minutes
User A takes Action X again -> Reschedule task T1 to occur in 10 minutes
User B takes Action X -> Reschedule task T1 to occur in 10 minutes

Basically, I want task T1 to occur 10 minutes after the last occurrence of Action X.  This has the side-effect that T1 may never occur, so you need to account for that, perhaps having a Cron job to enforce the task periodically, but I want to avoid running T1 repeatedly (or running multiple instances of T1 concurrently).

Perhaps you could add a name_reuse_period to the Task class to govern the tombstone reset on the task name and default it to the current seven day period.

I have forwarded this request to the engineering team. We will update this issue with any progress updates and a resolution.