Batch Processing
Large sync and automation workloads already move through Messenger, app queues, and dedicated consumers so heavy processing can run outside the request cycle.
Batch Processing Queue
Monitoring background jobs and tasks
How it works in the app
Heavy work is queued selectively instead of universally. Messenger messages, app-specific queue names, and dedicated consumers are used for integrations, workflows, and other long-running jobs.
There is also an app queue manager that starts, tracks, and cleans up consumers per installed app, which is why sync-heavy modules can run asynchronously without tying everything to a single request.
Included in the current implementation
Messenger-backed async processing
Dedicated queue consumers per app
Workflow and integration job isolation
Operational queue supervision
Need async work to stay off the request path?
Indexed PIM already uses queues where operational load justifies background execution.