Skip to main content


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

Job schedulers (agents) that clean up history records

Updated on January 31, 2022

Pega Robot Manager adds new job schedulers (agents) to clean up excessive history records.

pyArchiveRoboticAutomations
Archives excess records of robotic automations from History-Data-Robot-Automations (database table: pr_data_robot_automation_audit).
pyArchiveRoboticEvents
Archives excess records of robotic events from History-Data-Robot-Events (database table: pr_data_robot_event_audit).
pyPurgeRobotOperatorHistory
Purges excess records of robotic operator and service operator from History-Data-Admin-Operator-ID (database table: pr_history_data).

For each of these job schedulers, you can specify the number of latest records to retain (recordsToPreserveForEachRobot). All older records exceeding this number will be automatically archived.

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