3689454 - Objects not archived in the expected date

The archiving was configured in SAP Cloud for Customer and even though there are objects that match the criteria, the objects were not archived in the expected archiving date. It is desired to know if it can be delays with the archiving date for the objects and why.

SAP Cloud for Customer

The archiving job always sorts the last change date time in ascending order to pick the packages to process and runs for specified time. One thing which changes is the top row, it gets changed with each run if it is not able to find any record on a particular day. Second day it start the job from that top row + 1.

Hence, for example, if there are 200 Tickets in the system, it will get 100 and see how many of these 100 matches the archiving criteria. In the other day, it will start from Ticket 101 onwards. 

Also, the first part of the job "Collect and Verify" runs for at max one hour. After that time (or earlier if all candidates are verified) these verified instances are handed over to a second part "Archive and Delete". System can verify between 80.000 and 120.000 instances during this hour.
 
Therefore, If for example, the system has more than 5 million Tickets, then due to the behavior described above the objects (in this example Tickets) eligible for archiving can be archived days after the expected archiving date.

SAP Community: Archiving - How it is designed, how does it work 

selected date, last changed on, retention period, tickets, sales orders, sales quotes, opportunities, leads, phone calls, appointments, e-mails, email, mail, visits, C4C, archiving, archived, archive, move2archive, ARCWB , KBA , LOD-CRM-ARC , C4C Archiving , LOD-CRM-OPP , Opportunity Management , LOD-CRM-SRP , Service Request Processing , Problem

SAP Cloud for Customer core applications all versions