Skip to main content
Version: 2026.1

Symfony Messenger

Pimcore uses the Symfony Messenger for background processing of maintenance tasks, search indexing, and other asynchronous operations.

Transport Configuration​

The messenger transport DSN is configured via the PIMCORE_MESSENGER_TRANSPORT_DSN_PREFIX environment variable. The installer sets this automatically based on the chosen transport backend. Each transport's DSN is formed by appending the queue name to the prefix:

TransportPIMCORE_MESSENGER_TRANSPORT_DSN_PREFIXExample Queue DSN
Doctrine (default)doctrine://default?queue_name=doctrine://default?queue_name=pimcore_core
AMQP (RabbitMQ)amqp://guest:guest@rabbit:5672/%2f/amqp://guest:guest@rabbit:5672/%2f/pimcore_core
Redisredis://redis:6379/redis://redis:6379/pimcore_core

To switch transports, change only the env var and restart workers. No YAML editing is needed.

Handle Failed Jobs​

If jobs fail during processing, they are discarded from their transport after a defined number of retries. You can redirect failed jobs to a dedicated transport instead of discarding them:

framework:
    messenger:
        transports:
            pimcore_failed_jobs:
                dsn: '%pimcore.messenger.transport_dsn_prefix%pimcore_failed_jobs'

            pimcore_core:
                dsn: '%pimcore.messenger.transport_dsn_prefix%pimcore_core'
                failure_transport: pimcore_failed_jobs

The pimcore.messenger.transport_dsn_prefix parameter resolves from the PIMCORE_MESSENGER_TRANSPORT_DSN_PREFIX environment variable, so the failed jobs transport automatically uses the same backend (Doctrine, AMQP, or Redis) as all other transports.

Failed jobs can be re-processed later after fixing the underlying issue:

bin/console messenger:consume pimcore_failed_jobs

See the Symfony documentation for more options on failed job processing.

RabbitMQ is the recommended message queue for production use.

Resources: