Okta System Log Omits Import Complete Event for Active Directory Incremental Imports
Last Updated:
Overview
Okta omits the completion event log for Active Directory (AD) incremental imports when no directory changes occur. This behavior is expected, and administrators can verify the import status on the Import Monitoring page to confirm zero updates. When an incremental import runs but finds no updated timestamps or changes, Okta does not generate a completion log event. Administrators observe that scheduled incremental imports complete successfully, but the System Log does not display a completion event.
Applies To
- Okta Identity Engine (OIE)
- Okta Classic Engine
- Active Directory (AD) Incremental Imports
- System Log
Solution
Why does Okta omit the import complete events in the System Log for some incremental imports?
An incremental import captures changes in the directory that occur only since the last import. If Okta does not detect any timestamp-based change tracking on AD, Okta provides only specific System Log events.
Review the following images displaying the specific System Log events that Okta provides when no timestamp-based changes occur in AD.
Verify the import status by reviewing the following image of the Import Monitoring page, which displays zero updates for all user and group objects.
During an incremental import event, whenever Okta does not detect an updated timestamp from the last import process, Okta omits the system.import.complete event log.
