Issues with Export/Import Audit on table rotationSummaryCustomers sometimes faces issues like the audit data is being not pulled from sys_audit table to build History set. The reason for this is how the system works with Audit and History Sets. Basically, each record's History Set will be generated when a record is inserted if the record is on an audited table. A user must then view a record for the system to create or update a history set (and history set lines) for that record. There is a catch. The system will only generate history set lines from the audit (or email) records by looking at the table rotation schedule's "valid from" and "valid to" dates. If a record's creation date (sys_created_on) exists in a table rotation schedule (also known as "partition") that does not fall within the specified date and time window, then it will simply be ignored when generating the history set lines.Related LinksIt is recommended not to export/import the audit data when the tables are in Rotation. It might generate the history for few records not for all. Schedule clone with “Exclude Audit data” unchecked.