Unexpected Record getting ArchivedIssue Records are being archived even though Archive rule is inactive OR do not match the filter conditions of the archiving rules. ReleaseALLCauseThe most common cause is that users are manually archiving the records. A customer may also change the archive rules by accident.ResolutionIn order to identify who/what archived the particular record you can take any of the below actions: Check the sys_archive_log table for the sys_id of the archived record; the Created By column will show the user that archived the record. You can also see the archive run / archive rule, if the record was archived via a ruleIf the record was archived recently (last 4 days), you can check the Localhost logs at the exact time of the record being archived and see the corresponding messages.On reviewing the localhost logs around the time the record was archived look for the glide.db.archiver thread , if not present then look for a user UI Action (Archive Record) If trying to Archive a record using the 'Archive Record' UI Action you might receive "No archive table defined in the Archive Map for: <TABLE_NAME>" message on the Header. This will only be observed when the Archive Rule hasn't been Run/Triggered previously and no ar_<Table_name> is present. If the ar_<Table_name> is present already due to the previous run, the UI Action (Archive Record) will show the Archive Rule in the Archive field under Archive Run even though Rule is in inactive state.