title: GCP Cloud Tasks: shorten period for creating a previously created named task
body: <p>We are developing a GCP Cloud Task based queue process that sends a status email whenever a particular Firestore doc write-trigger fires. The reason we use Cloud Tasks is so a delay can be created (using scheduledTime property 2-min in the future) before the email is sent, and to control dedup (by using a task-name formatted as: [firestore-collection-name]-[doc-id]) since the 'write' trigger on the Firestore doc can be fired several times as the document is being created and then quickly updated by backend cloud functions.</p>
  <p>Once the task's delay period has been reached, the cloud-task runs, and the email is sent with updated Firestore document info included. After which the task is deleted from the queue and all is good.</p>
  <p>Except:</p>
  <p>If the user updates the Firestore doc (say 20 or 30 min later) we want to resend the status email but are unable to create the task using the same task-name. We get the following error:</p>
  <pre><code>409 The task cannot be created because a task with this name existed too recently. For more information about task de-duplication see https://cloud.google.com/tasks/docs/reference/rest/v2/projects.locations.queues.tasks/create#body.request_body.FIELDS.task.
  </code></pre>
  <p>This was unexpected as the queue is empty at this point as the last task completed succesfully. The documentation referenced in the error message says:</p>
  <blockquote>
  <p>If the task's queue was created using Cloud Tasks, then another task
  with the same name can't be created for ~1hour after the original task
  was deleted or executed.</p>
  </blockquote>
  <p>Question: is there some way in which this restriction can be by-passed by lowering the amount of time, or even removing the restriction all together?</p>