Skip to main content


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

Managing background processing resources

Updated on July 8, 2022

Meet highly challenging background processing requirements by creating job scheduler rules to run scheduled tasks and queue processor rules for asynchronous processing.

  • Background processing best practices

    To maintain and manage your work resources and to ensure that resource performance is not compromised if a node becomes unexpectedly unavailable, design your work assignments to be thread-safe and use a multi-threaded environment.

  • Using job schedulers and queue processors instead of agents

    For better scalability, ease of use, and faster background processing, use job scheduler and queue processor rules instead of agents in scenarios that previously required agents, such as service-level agreements, sending daily emails, or queuing items.

  • Managing job schedulers

    Job schedulers are internal background processes on the server that run activities on a periodic basis. Use the Jobs landing page to manage job schedulers in your application.

  • Managing queue processors

    Use the Admin Studio, Queue processor page to review information about queue processors in your system.

  • Managing agents

    Use Admin Studio to manage agents to debug and trace any problems with agent activity. You can also start, stop, restart, or trace agents.

  • Automating the runtime context management of background processes

    You can enable your system to automatically manage the resolution of queue processor and job scheduler rules in an application without any manual configurations. You must add your application's custom job scheduler roles to the SRC page directly. These applications are added to the System Runtime Context.

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.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us