Change Tracking sometimes returns new inserts without primary key values

We utilize Change Tracking feature to catch inserts and updates for couple of tables. Queries are like this: SELECT P.* ,CT.SYS_CHANGE_OPERATION ,TC.commit_time FROM schema.tablename AS P RIGHT OUTER JOIN CHANGETABLE(CHANGES schema.tablename, 438750) AS CT ON CT.ID = P.ID LEFT OUTER JOIN sys.dm_tran_commit_table TC on CT.sys_change_version = TC.commit_ts WHERE SYS_CHANGE_OPERATION IN ('I','U') /* INSERTS and UPDATES */ AND SYS_CHANGE_VERSION <= '439766' /* = CHANGE_TRACKING_CURRENT_VERSION */ From time to time results may contain new inserts which doesn't have primary keys. Below there's an example of one case. First row is a header and in this case the first column (ID) is primary key. First four rows are ok but after that we have these odd cases which are listed being as type SYS_CHANGE_OPERATION="I" (=insert) but all values are missing, including primary key: Does anyone have ran into similar issues using Change Tracking? What could be the reason for this kind of behaviour?