Skip to main content

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

Job scheduler FAQ

Updated on July 8, 2022

A job scheduler rule is a background process that you can use to manage recurring and scheduled tasks throughout your Pega application.

Frequently Asked Questions about the job scheduler include the following:

What attributes can I set for the job scheduler?

For detailed information, see Job scheduler rules.

How do I monitor and diagnose issues with job schedulers?

On the Admin Studio Jobs landing pages, which shows you the list of current job schedulers running in the system, with options to trace them and enable or disable them. Pega also provides REST APIs to perform these operations. The swagger UI for the REST APIs is available as part of ResourcesPega API.

For more information on managing job schedulers, see the following:

How do I enable diagnostic logging for job scheduler?

You can identify and track relevant or specific log entries for specific job schedulers, such as job scheduler creation, updates, registration, scheduling, and activities. For more information, see Details provided in background processing logs.

How does job scheduler relate to agent functionality?

In Pega Platform version 8.1, job scheduler replaced advanced agents for recurring and scheduled tasks. For details, see Background processing best practices.

Will the agents in earlier versions of Pega Platform still work after 8.x?

Yes they will, but eventually you may need to convert agents to job schedulers.

Does Pega Platform have any default job schedulers?

Yes. Pega Platform provides default job schedulers. For descriptions of a few examples, see Node and cluster default job schedulers.

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