Issue with SGC data scource after instance or application upgradeIssue The issue was observed in the following two scenarios: => Post Application Upgrade: After upgrading the application, the data source execution did not pull any data, and no errors were observed during the import set execution. => Post Instance/Application Upgrade: The data source started throwing the following error after the instance or application upgrade. 2025-05-05 21:54:29 (341) worker.0 worker.0 txid=e194859e1b15 tx_pattern_hash=690916352 LocalhostTransactionLogger *** End Parallel Job Executor - system, user: system, total time: 0:00:01.014, processing time: 0:00:01.014, CPU time: 0:00:00.792, SQL time: 0:00:00.129 (count: 368), business rule: 0:00:00.307 (count: 22), Cache build time: 0:00:00.010, Script time: 0:00:00.365 (count: 63), Total memory allocated: 219.15MB, type: scheduler, origin scope: sn_cmdb_int_util, app scope: sn_cmdb_int_util2025-05-05 21:54:29 (340) worker.0 worker.0 txid=e194859e1b15 JobExecutor Completed: Parallel Job Executor in 0:00:01.006, next occurrence is 2025-05-06 04:55:28, id=ee4315031b01221058f85357624bcb89 tr=1 pr=100 re=60 po=1746507268 la=0.332 c=t2025-05-05 21:54:29 (326) worker.0 worker.0 txid=e194859e1b15 SysLog SEVERE *** ERROR *** System Parallel Job: Exception while executing the job:com.glide.db.impex.custom.parallel.ParallelDataLoaderJob.executeTask(ParallelDataLoaderJob.java:105)com.glide.system_parallel_job.impl.ParallelJobExecutor.execute(ParallelJobExecutor.java:84)com.glide.schedule.JobExecutor.lambda$executeJob$1(JobExecutor.java:195)com.snc.db.data_replicate.replicator.DataReplicationAdvisors.runInOriginatorContext(DataReplicationAdvisors.java:74)com.glide.schedule.JobExecutor.lambda$inDataReplicationContext$3(JobExecutor.java:225)com.glide.schedule.JobExecutor.executeJob(JobExecutor.java:198)com.glide.schedule.JobExecutor.execute(JobExecutor.java:178)com.glide.schedule.JobExecutor.execute(JobExecutor.java:168)com.glide.schedule_v2.SchedulerWorkerThread.executeJob(SchedulerWorkerThread.java:609)com.glide.schedule_v2.SchedulerWorkerThread.lambda$process$2(SchedulerWorkerThread.java:402)com.glide.worker.TransactionalWorkerThread.executeInTransaction(TransactionalWorkerThread.java:35)com.glide.schedule_v2.SchedulerWorkerThread.process(SchedulerWorkerThread.java:402)com.glide.schedule_v2.SchedulerWorkerThread.run(SchedulerWorkerThread.java:178)2025-05-05 21:54:29 (319) worker.0 worker.0 txid=e194859e1b15 ImportLog SEVERE *** ERROR *** Error while executing the executeTask method in context : 5d948d9e1b156e5458f85357624bcbb8 :com.glide.system_parallel_job.ParallelJobException: Data was not loaded properly with data source : SG-AWS-Security-Group2025-05-05 21:54:29 (313) worker.0 worker.0 txid=e194859e1b15 ImportLog SEVERE *** ERROR *** Data was not loaded properly with data source : SG-AWS-Security-Group2025-05-05 21:54:29 (309) worker.0 worker.0 txid=e194859e1b15 ImportLog WARNING *** WARNING *** Loading import set table cancelled: sn_aws_integ_sg_aws_security_group2025-05-05 21:54:29 (304) worker.0 worker.0 txid=e194859e1b15 AbstractProgressWorker SEVERE *** ERROR *** com.glide.db.impex.custom.parallel.ParallelJobLoadercom.glide.db.impex.datasource.DataSourceException: TypeError: Cannot read property "operationType" from undefined (sys_script_include.0dbb928e53203010a3e4ddeeff7b1298.script; line 99)at com.glide.db.impex.custom.CustomLoader.loadDataFromScript(CustomLoader.java:88)at com.glide.db.impex.custom.CustomLoader.load(CustomLoader.java:57)at com.glide.db.impex.custom.parallel.ParallelJobLoader.load(ParallelJobLoader.java:57)ReleaseIssue is specific to SGC application upgrade scenarioCauseThe issue is occurring due to differences in the data loader script configured on the data source. You can compare the out-of-the-box (OOTB) data loader script with the one used in the data source where the issue is observed.Resolution Solution-1:- ******** To resolve this issue, navigate to the Fix Scripts module and identify the appropriate fix script for your Service Graph Connector (SGC) application. For SGC for Azure, the latest fix script is usually titled "Fix Script SG-Azure 1.12 Parallel Loading Fix" or a newer version.For SGC for AWS, the relevant script is named "SGC - Parallel Loading Fix Script". Once you've located the correct script, open it and click on "Execute Script". This should address the parallel loading issue. Solution-2:- ********* If the customer is using SGC for AWS version 2.10.1 or later, please verify the Data Loader script. In some cases, the line "partition_info: partition_info" may be missing. Adding this missing line typically resolves the issue.The script provided below is specific to version 2.10.1. If the customer is using a newer version, we recommend installing the corresponding version of SGC for AWS appliacation and comparing the Data Loader script in the customer instance against the out-of-the-box (OOTB) script. Data loader script from 2.10.1:- (partition_info arguements are passed)**********************************************************************(function loadData(import_set_table,partition_info) {import_set_table.addJSONColumn("u_data");var args = {connection_alias_id: "c3f0b8c453b32010c23bddeeff7b12ee",data_source_id: "ba8b528e53203010a3e4ddeeff7b120a",partition_info: partition_info};new SgAwsSecurityGroupUtils(args).loadData(import_set_table);})(import_set_table,partition_info);