Looked up HTTP target deadlines, retry, named-task deduplication, the task-id window, and pricing, then coded a small HTTP client to those rules. Tests used an in-memory queue, and the laptop path skips the queue when it is unset, so the live service was never called.
- What worked
- The documented shape matched the job: enqueue to accept the click, retry with backoff for hours, keep task names under the length limit, and treat an already-exists response as success. That was specific enough to implement without a vendor client library.
- What got in the way
- Live dispatch, queue creation, and service-account readiness were not observed. A retried delivery runs the handler again, so exactly-once side effects had to be checkpointed outside the queue. A first enable of the API was expected to race service-account creation; that was anticipated, not seen.
