Additionally, you can validate that your case archival process succeeded by running a report for cases that are resolved per their archival policy before and after running the archiving process. The difference in reports shows cases that Pega Platform purged from the primary database and copied to Pega Cloud File Storage.

You can review if Pega Platform archived a specific case by searching for archived work items in the Case Management Portal.

For more information, see Reviewing archived case data.

Using logs to troubleshoot your archiving and purge process

If your archival process did not run as expected, you can obtain the log files for troubleshooting.

1. Enable the following loggers:
   • datastoreexecutor.crawler.CaseCrawler
   • datastoreexecutor.Archiver.CaseArchivalStrategy
   • datastoreexecutor.databroker.IndexManagerService
   • com.pega.platform.datastoreexecutor.purger.internal.PurgerImpl

   For more information about viewing logs, see Viewing logs.

2. Access your log files.
   1. Use Kibana to access your log files.

      Job Schedulers run on any available node. You can access the logs of your archiving and purge jobs regardless of what node they run on by using Kibana.

      For more information, see the article Accessing your server logs using Kibana.

   2. Optional: If you cannot use Kibana, use activities to run archive and purge on your local node:

      Instead of running the pyPegaArchiver, pyPegaIndexer, pyPegaPurger jobs, run the following activities:

      Note: Run the activities in the following order.
      • pzPerformArchive
      • pzPerformIndex
      • pzPerformPurge

      For more information about using activities, see Creating an activity.

      The PegaRules log gets created on the node on which you run the activity.