@VishruthiReddy

Here’s the clean way to get a per-day list: each archive ZIP written by the in-memory pipeline contains a CSV “manifest” with one row per archived item (columns include pzInsKey, pxObjClass, parentInsKey, pzPVStream), and the folder path already encodes the archive date, so you can treat that CSV as the source of truth for “which cases were archived on a given day.”  Point a Repository (PCFS) or a File Data Set at /archive/archivedclasses/<Your-Work-Class>/<YYYY>/<MM>/<DD>/, iterate all ZIPs for that date, use the Repository API to fetch each file, unzip, parse the CSV, and store/show the list (either write to a custom table or drive a simple report).  If you can’t browse PCFS directly, use the Dev Studio Repository browser or ask Pega Cloud to grant read access for that path. For run-level context and counts, use the in-memory pipeline job (pyPegaArchiverUsingPipeline) plus the Archival results/Log-ArchivalSummary views to correlate which ZIPs were produced in that window.Portal search (pySearchFieldWorkResponsive) is fine for quick lookups but won’t show the archive date or guarantee membership of a specific run—use the manifest instead. If you need to restore or inspect more, follow the “Retrieving archived Case data” guidance; but for daily auditing, the manifest is the reliable list.