In IIQ’s new access history feature, account changes show up on the timeline, along with other data. However, we observed that when an account is changed, the changes sometimes don’t show until much later. We determined that this happens when the Link is updated, but the Identity is not.
When the Identity is updated, IIQ creates a new Identity capture ID and full capture document in spt_hist_identity_capture.
When an account changes, a “patch” document is inserted into spt_hist_account_capture and is associated with the capture_id of the current Identity capture. However, the date of the patch is later than the Identity capture effectiveDate.
The UI queries for the latest capture ID, then queries for events associated with that capture ID. However, it appears to only pull events earlier than the capture. This means that account changes after the latest identity capture, while associated with its ID, do not appear in the UI. When something else later updates the Identity, the account changes suddenly appear.
This is not a limitation of the data. If you invoke the /events endpoint without passing a capture ID, the proper events are returned.
I strongly suspect this is also the case in IDN.