IssueTracker

This will create a feature request which anybody can view and comment on.

Please describe your requested enhancement. Good feature requests will solve common problems or enable new use cases.

What you would like to accomplish:

The current task de-duplication time is roughly one hour (up to four hours I believe in the documentation). It would be helpful to be able to configure this time as a TTL from the last successful task execution. If not possible, for purposes of development and testing, it would be helpful to have a "Purge Deduplication IDs" endpoint.


How this might work:

TTL - Set a seconds value for task deduplication. When the task checks for previously successful tasks with the same name, it only blocks the task if (now - last_successful_execution) is < queue.deduplication_ttl

Purge Deduplication IDs- A button and corresponding rest endpoint that clears the ids/keys used to deduplicate.


If applicable, reasons why alternative solutions are not sufficient:

For deduplication purposes, everyone has a different use case. Some organizations might now want to send more than one customer email per hour, some may wish only to deduplicate when changes in multiple tables trigger task creation, and might want a time to live or deduplication time of 5 minutes or less.

For development purposes, when I want to clear the deduplication keys/ids to test something, I could generate the tasks with different names, however in my situation the tasks for one queue are created in many different functions, and using a naming schema passed between the functions would be a lot of overhead.


Other information (workarounds you have tried, documentation consulted, etc):

There seems to be some confusion around this feature, and others interested in being able to control deduplication time.
https://stackoverflow.com/questions/63694524/gcp-cloud-tasks-shorten-period-for-creating-a-previously-created-named-task