Scheduled import not running: import set job inactive

The scheduled data source or import set definition has been manually deactivated in the Data Source configuration. (high likelihood)

The 'Run as' user specified in the scheduled job is locked, inactive, or has insufficient permissions to execute the import. (high likelihood)

Another import job for the same data source is currently running and blocking the scheduled execution in the import queue. (medium likelihood)

The import set table or transform map associated with the scheduled job has been deleted or corrupted. (medium likelihood)

System maintenance mode or import processing has been globally disabled via system properties. (low likelihood)

Step 1: Navigate to System Import Sets > Data Sources and locate the failing scheduled import to verify its Active field is checked.

Step 2: Check the Scheduled Import Jobs table (sys_import_set_job) to confirm the specific job record exists and its State field shows Active.

Step 3: Verify the 'Run as' user in the scheduled job is active by navigating to User Administration > Users and checking the user account status and last login.

Step 4: Review the Import Set Run table (sys_import_set_run) to identify any currently running imports that might be blocking the queue for the same data source.

Step 5: Confirm the associated import set table still exists in the database by searching All Tables for the table name specified in the data source configuration.

Step 6: Check system properties glide.import.enabled and glide.scheduled_import.enabled are set to true under System Properties > System.

Step 7: Test the import manually by opening the data source record and clicking Test Load Data to verify the import configuration is functional.

Step 8: If all configurations appear correct, restart the scheduled job by deactivating and reactivating the data source or manually triggering a run.