Table Name	Reason for Exclusion	Cascade Delete
AcceptedEventRelation	Subset of EventRelation table	False
AttachedContentDocument	Salesforce limitation - not queryable	True
CombinedAttachment	Salesforce limitation - not queryable	True
ContentVersion	-	False
DeclinedEventRelation	Subset of EventRelation table	False
EventFeed	Subset of FeedItem table	True
UndecidedEventRelation	Subset of EventRelation table	False

When the archive job purges event records, records from the excluded child tables that have cascade delete set to true will also be purged by Salesforce. Some tables are excluded from the entity because they are a subset of another table. Even though data from these tables is purged by Salesforce, there is no data loss on the subset tables because the same data is available in the superset table, which is part of the Event entity.

Note that some tables are excluded from the entity because they are not available unless features like tag, shared activites, and network communities are enabled.

In the Salesforce Event page, there is an option to create a meeting request using the

New Meeting Request

button. Once the meeting is created, by default it will exist in an "Unconfirmed" state. In an unconfirmed state, some of the event columns like "EndDateTime" and "StartDateTime" are empty. Because of this unconfirmed state, records will not be included in an archive or purge job.