Skip to main content

         This documentation site is for previous versions. Visit our new documentation site for current releases.      

Queue Processor

Updated on October 8, 2023


This content applies to On-premises, Client-managed cloud and Pega Cloud environments

Queue Processors were introduced in Pega 8 to replace standard agents. Queue Processors leverage Kafka, which increases throughput and improves performance at the database level.

For more information about Queue Processors, see:

How to identify

The rows in the output report from the Pega Cloud Readiness Tool are:
Area:  Asynchronous Processing
Rule Type:  Rule-Agent-Queue
Details column:  Leverage queue processors to replace standard agents for queue management and asynchronous processing

If the text in the Details Column is “Leverage job schedulers to replace advanced agents for recurring or scheduled tasks,” see the “Job Scheduler” section.

How to modernize

Use Queue Processors to manage asynchronous processing.  This was previously done by standard agents, but Queue Processors provide more flexibility.

The new Queue Processor rules can be configured to enhance the performance of background processing.  They can be configured to scale both horizontally (increasing the number of nodes executing the Queue Processor) and vertically (increasing the number of threads dedicated to run the Queue Processor on each node).

For more information about replacing standard agents with Queue Processors, see Replacing an agent with a queue processor rule for real-time messages

When switching from standard agents to Queue Processors on a Production environment, be sure that all the items queued for the standard agent are consumed before turning off the agent.  For more information, see Replacing an agent with a queue processor rule for delayed messages


Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best. is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us