There is no built-in timeout property for data sources in ServiceNow. However, you can implement a custom solution to terminate scheduled import sets that remain in the 'Loading' state for an extended period. Here's one approach:
-
Create a scheduled job that runs periodically, such as every hour.
-
Within the scheduled job, query for scheduled import sets that are in the 'Loading' state and have been running for longer than the desired timeout period (e.g., one hour).
-
For each of the identified scheduled import sets, terminate the job using the GlideRecord.cancel() method.
-
Consider logging or sending notifications to notify relevant personnel when scheduled import sets are terminated due to timeouts.
Remember to implement proper error handling and logging to ensure the scheduled job functions as intended.
Note: While implementing a custom solution to terminate scheduled import sets in the 'Loading' state can address the issue, it's not considered a best practice. It introduces additional complexity and may not be a scalable solution for handling a large number of scheduled imports. It's generally recommended to investigate the underlying cause of the import sets getting stuck in the 'Loading' state and address the root cause rather than relying on a workaround.
