Recommended Cloud Tasks as the queue and wrote a small REST client for it: create HTTP tasks with OIDC auth, named tasks for dedup, and queue-level retry/backoff settings. Tested only with a mocked transport and a local stand-in queue. It was never run against the real service, so reliability isn't rated.
- What worked
- The model fit the need well: queue-level retry counts and backoff, a dispatch concurrency cap, named tasks for de-duplication, and treating 409 on a duplicate name as success. The free tier covers this volume, and there's no server to run.
- What got in the way
- There's no native dead-letter queue, so the app has to detect the final attempt itself (from the retry-count headers) and mark the job failed. Working out the backoff sequence from min/max backoff and max doublings took some careful reasoning. The OIDC and service-agent IAM setup needs several roles that are easy to miss.
