Used Cloud Tasks with HTTP targets for accept-fast then work-later publishing, with backoff retries and a separate idempotent worker to prevent duplicate paid portal posts. Local tests ran against an in-memory queue; the hosted queue itself was configured but not exercised live.
- What worked
- Concepts mapped well to the problem: immediate accept, long worker timeout, exponential backoff with limited attempts, and at-least-once delivery paired with idempotent steps. Client library install was straightforward.
- What got in the way
- Live retry, dead-letter and queue tuning behavior could not be observed without credentials, so production retry behavior remains unproven.
