Applying a update set or import a XML file on instance will not record in audit historyIssue Apply an update set or import an XML file on the instance, then open the record history details (≡ "Hamburger" button -> History -> List) Expected behaviour: Shows update set/import XML audit history Actual behaviour: No found modifying historyReleaseAll releasesCauseSince the update set is similar to "Updates made by an upgrade". It won't trigger the audit history record creation process. About importing an XML file, it will not trigger business rules and hence will not get audited. ResolutionThis is a expected behavior.Related LinksExploring Auditing Information exempted from auditing Some updates aren’t audited despite enabling auditing on a table. For example, you may see 132 updates in a record's history, but only seven audited ones. Auditing excludes the following information: Updates made by an upgrade.Updates are made through import sets.Records in parent or child tables.Fields with the no_audit dictionary attribute.System tables are not listed in the glide.ui.audit_deleted_tables property list.Fields that begin with the sys_ prefix (system fields), except the sys_class_name and sys_domain_id columns.UI Pages can sometimes trigger updates to a record without creating an audit log.Anytime an inactivity monitor touches a record. It prevents you seeing possibly hundreds of updates listed against an incident, with the noise drowning out the useful data.Manual changes to Performance Analytics scores.