Does @Will Cho 's discussion  Archive case and its associated artifacts help here?

@Chetan.Chaudhari please could you comment on this question?

⚠ Below is a GenAI-powered tool. All generated answers require validation against the provided references.

The pyPegaIndexer Job Scheduler indexes the copied files into Elasticsearch. The index keeps the association between an archived case and its archived file in the secondary storage. If there's a need to delete and reindex data, the pyArchival_ReIndexer Job Scheduler can be used to fix corrupted Elasticsearch indexes. However, if the data has been deleted from the main table because it has been moved to the archive, Pega platform doesn't realize this and thus Elastic Search would not know. Therefore, the index will contain the old data unless a full re-index is triggered from the search landing page for that class or set of classes. As of now, Pega cannot track changes to tables which are not going through Obj-Save / Obj-Delete methods for the index to be updated. You could potentially write triggers on these tables which upon delete could populate the pr_sys_queue_ftsindexer table with the pzInsKeys of the records deleted. But this will cause duplicate entries during normal deletes (obj-delete).