Fields Excluded from "user.updated" Atuh0 Event Stream Trigger
Last Updated:
Overview
This article explains why user.updated events in the event stream may not always correspond one-to-one with API calls. It details specific low-value fields (for example, lastLogin, loginsCount) whose changes do not trigger a user.updated event when they are the only modification, clarifying the expected behavior for data consistency.
Applies To
- Event Streams
- user.updated Trigger
- Auth0
Cause
This discrepancy is by design. To prevent high volumes of low-value event traffic, the system does not generate a user.updated event when the only modification to a user's profile is an update to specific fields like lastLogin, lastIP, updated_at, or loginsCount.
Solution
An inconsistency may be observed between the number of user.updated events received via the event stream and the number of user records modified through API calls. This is expected behavior and is implemented to manage the volume of event traffic.
The system is designed not to trigger a user.updated event if the only change to a user's profile is an update to one of the following low-value fields:
lastLoginlastIPupdated_atloginsCount
Because changes to these fields alone do not generate an event, a direct API query to export users (for example, filtering by updated_at > [timestamp]) will often return a higher count of updated records than the number of user.updated events received in the same timeframe.
The data provided by the event stream is accurate for the events it is designed to capture.
