Google Cloud Tasks Cost: Operations, Retries, and Workers

Cloud Tasks bills API calls and push delivery attempts as operations. The first 1 million operations each month are free, and the next tier is priced per million operations. One task commonly creates at least two operations—one create call and one successful delivery—so task count alone understates usage. List calls and other API actions can add more operations.

Payloads are metered in 32 KB chunks. A 96 KB task therefore counts as three operations when it is created and another three for a delivery attempt. Estimate monthly operations as API actions plus delivery attempts, multiply each by its payload-size chunks, subtract the current free allowance, and verify the latest tier price on the official Cloud Tasks pricing page.

Every push delivery attempt is billable, including retries caused by timeouts or unsuccessful worker responses. Model expected tasks × average attempts rather than assuming exactly one delivery. Cap attempts and retry duration, use exponential backoff, and make handlers idempotent so a repeated delivery does not duplicate database writes, messages, or paid third-party calls.

The Cloud Tasks line item excludes the service that handles the task. Add Cloud Run, Functions, App Engine, database, logging, and external API usage generated by every attempt. HTTP targets can also incur normal network charges, so keep the queue and worker close when the architecture permits and price the actual network path.

Queue rate limits apply to first attempts and retries. Set maximum dispatches per second and maximum concurrent dispatches to match the worker's safe capacity. This smooths bursts and reduces 429 or 503 responses that can trigger more attempts, increase latency, and raise downstream compute or database cost.

Monitor task-attempt count, response codes, queue depth, and worker duration together. A cheap queue can still expose an expensive or overloaded target. Test the estimate with normal traffic, a failure spike, and a scheduled burst so the budget includes both Cloud Tasks operations and the full cost of processing them.

Compare Cloud Tasks with Cloud Run jobs and scheduled workloads.