When are Scheduled Imports Triggered in Okta
Last Updated:
Overview
Scheduled imports in Okta trigger based on the completion time of the previous import job, which causes a drift in the start time. Understanding this behavior helps administrators anticipate import schedules. Customers should utilize the "Cron based User Import scheduling" Early Access feature to control exact trigger times.
Applies To
- Okta Identity Engine (OIE)
- Okta Classic Engine
- Okta Integration Network (OIN)
- Scheduled Imports
Cause
Scheduled imports trigger automatically after the configured amount of time passes from the completion of the previous import job. The import completion time depends on the amount of data changed between the two imports. For example, if a scheduled import set to run once a day starts at 6:00 PM and completes at 6:05 PM, the next import starts at 6:05 PM the following day.
Solution
How do customers control the exact time an import triggers?
Okta provides an Early Access feature named "Cron based User Import scheduling" to control the exact time an import triggers. Enable the Cron based User Import scheduling feature by navigating to the Features section of the Settings menu in the Okta Admin Console.
- Navigate to the Okta Admin Console.
- Choose Settings.
- Select Features.
- Enable Cron based User Import scheduling.
NOTE: This feature does not apply to Scheduled Imports for Active Directory (AD) or Lightweight Directory Access Protocol (LDAP).
