usage.md

Usage basics

Usage

For example, if you need to download and save a file, you can create a message like this:

$message = new \Yiisoft\Queue\Message\Message(
    RemoteFileHandler::class,
    ['url' => $url, 'destinationFile' => $filename]
);

Here's how to push a message to the queue:

$queue->push($message);

To push a message that should be processed after 5 minutes:

Delayed execution is implemented using the DelayEnvelope. The envelope wraps your message with delay information that adapters can use if they support delayed execution.

use Yiisoft\Queue\Message\DelayEnvelope;

$delayedMessage = new DelayEnvelope($message, 5 * 60); // 5 minutes delay
$queue->push($delayedMessage);

Important: Adapters that support delaying will use the delay information from DelayEnvelope to schedule the message accordingly. Adapters that don't support delaying will ignore the delay data and process the message in the queue order.

Queue handling

Most adapters can be consumed using console commands registered by yiisoft/queue in your application. For more details, check the respective adapter documentation.

If you configured multiple queue names, you can choose which queue to consume with console commands:

yii queue:listen [queueName]
yii queue:run [queueName1 [queueName2 [...]]]
yii queue:listen-all [queueName1 [queueName2 [...]]]

Message status

use Yiisoft\Queue\MessageStatus;
use Yiisoft\Queue\Message\IdEnvelope;

$pushedMessage = $queue->push($message);
$id = $pushedMessage->getMetadata()[IdEnvelope::MESSAGE_ID_KEY] ?? null;

if ($id === null) {
    throw new \RuntimeException('The adapter did not provide a message ID, status tracking is unavailable.');
}

$status = $queue->status($id);

// Check whether the message is waiting to be handled.
$status === MessageStatus::WAITING;

// Check whether a worker has picked up the message and is handling it.
$status === MessageStatus::RESERVED;

// Check whether the message has been processed.
$status === MessageStatus::DONE;

For details and edge cases, see Message status.

Limitations

Messages are pushed in one process and consumed in another. Avoid relying on in-process state (open connections, cached objects, etc.) that may not be available in the worker process.

All data needed to handle a message must be included in the payload passed to getData().