Download the PHP package stackkit/laravel-google-cloud-tasks-queue without Composer

Cloud Tasks Queue Driver for Laravel

This package allows you to use Google Cloud Tasks as the queue driver in your Laravel application.

_{Companion packages: Cloud Scheduler, Cloud Logging}

Requirements

This package requires Laravel 12 or 13.

Installation

Require the package via Composer:

Add a new queue connection to config/queue.php:

Set the appropriate environment variables:

If you're using Cloud Run:

If you're using App Engine:

Refer to the table below for descriptions of each value:

Optionally, you may publish the config file:

If you're using separate services for dispatching and handling tasks, and your app should only dispatch jobs (not handle them), you may disable the task handler in config/cloud-tasks.php:

Cloud Run Jobs

If you want jobs to be processed by Cloud Run Jobs instead of HTTP endpoints, you can configure the queue to trigger Cloud Run Job executions.

Why Cloud Run Jobs?

Cloud Run Jobs are ideal for long-running batch processing that exceeds Cloud Tasks HTTP timeout limits.

Cloud Run Jobs can run for up to 7 days.

Tip: Use seperate queue connections with different targets, for low latency jobs, use HTTP targets, for longer running batch jobs use Cloud Run Jobs.

Setup

1. Create a Cloud Run Job with your Laravel application container, configured to run:

The command reads job data from environment variables passed to the Job by Cloud Run.

2. Configure your queue connection:

Note: The command reads CLOUD_TASKS_PAYLOAD, CLOUD_TASKS_TASK_NAME, and CLOUD_TASKS_PAYLOAD_PATH directly from environment variables at runtime using getenv(). These are set automatically by Cloud Tasks via container overrides.

3. Set environment variables:

Large Payload Storage

For jobs with payloads exceeding environment variable limits (32KB limit enforced by Cloud Run), configure a Laravel filesystem disk:

When the payload exceeds the threshold, it's stored in the disk and CLOUD_TASKS_PAYLOAD_PATH is used instead.

Note: The payloads will not be cleared up automatically, you can define lifecycle rules for the GCS bucket to delete old payloads.

How It Works

When you dispatch a job with Cloud Run Job target enabled:

1. Package creates a Cloud Task with HTTP target pointing to Cloud Run Jobs API
2. Cloud Tasks calls run.googleapis.com/v2/.../jobs/{job}:run
3. Cloud Run Jobs starts a new execution with environment variables set via container overrides:
   • CLOUD_TASKS_PAYLOAD - Base64-encoded job payload
   • CLOUD_TASKS_TASK_NAME - The task name
4. The container runs php artisan cloud-tasks:work-job which reads the env vars and processes the job

All Laravel queue functionality is retained:

• Job retries and max attempts
• Failed job handling
• Job timeouts
• Encrypted jobs
• Queue events

Required IAM Permissions

Cloud Run Jobs requires specific IAM permissions. Set these variables first:

Note: Find your Cloud Tasks service agent email in the IAM console under "Include Google-provided role grants". Note: Project ID and Project Number are different. Project ID is the name of your project, Project Number is the numeric ID of your project.

Project-Level Permissions:

Note: To restrict access to specific Cloud Run instances, use IAM conditions to limit access to specific Cloud Run Jobs / services.

Service Account Permissions:

How-To

Pass headers to a task

You can pass headers to a task using the setTaskHeadersUsing method on the CloudTasksQueue class:

You can also access the payload being dispatched:

Configure the task handler URL

Set the handler URL for a task using the configureHandlerUrlUsing method:

Or access the job being dispatched:

Configure worker options

Customize worker options using the configureWorkerOptionsUsing method:

Use a custom credentials file

Edit the client_options key in config/cloud-tasks.php:

Modify CloudTasksClient options

Edit the client_options key in config/cloud-tasks.php:

How it works & differences

Using Cloud Tasks as a Laravel queue driver is fundamentally different from other drivers like Redis.

With Redis or similar drivers, a worker listens for jobs via queue:work or queue:listen.
With Cloud Tasks, jobs are scheduled and dispatched via HTTP requests to your app.
There’s no need to run queue:work or queue:listen.

Good to Know

Cloud Tasks has its own retry configuration options like:

• Maximum number of attempts
• Retry duration
• Min/max backoff
• Max doublings

These are ignored by this package. Instead, you can configure retry behavior directly in Laravel.

Authentication

If you're not using your master service account (which has all abilities), assign the following roles to your service account to make it working:

1. App Engine Viewer
2. Cloud Tasks Enqueuer
3. Cloud Tasks Viewer
4. Cloud Tasks Task Deleter
5. Service Account User

Upgrading

See UPGRADING.MD for instructions on updating versions.

Troubleshooting

HttpRequest.url must start with https://

This can occur when your application runs behind a reverse proxy.
To resolve it, add your app’s domain to Laravel’s trusted proxies.
You may need to use the wildcard *.

Maximum call stack size (zend.max_allowed_stack_size - zend.reserved_stack_size) reached. Infinite recursion?

This seems to be a bug in PHP 8.3 and googleapis/gax-php.
See this issue for details.

A possible workaround is to disable the PHP 8.3 stack limit in php.ini:

Contributing

You can use the services defined in docker-compose.yml to run the package locally.

Inside the container:

1. Run composer install
2. Set up the environment: cp .env.example .env

Some tests use the Cloud Tasks API and require a project and credentials.
Set the appropriate variables in your .env.