IRE - NumberFormatException while exeuting Service Graph Connector.Issue It is observed that when the Service Graph Connect is triggered, the import set is showing "NumberFormatException". Below is the error stack.2022-04-08 09:31:03 (812) worker.0 worker.0 txid=eae887a81bf2 Identification Reconciliation Engine(IRE) Listener has started processing Transformed Messages2022-04-08 09:31:03 (820) worker.0 worker.0 txid=eae887a81bf2 SEVERE *** ERROR *** identification_engine : logId:[2209032c1bf2] Exception 'NumberFormatException: For input string: "null"' for payload from SG-CrowdStrike "items":[{"className":"cmdb_ci_network_adapter".............{"referenceField":"configuration_item","referencedBy":"4379032b94fd48564b6b46f03d4a9fe6|1653d797579942c0825e6a196dcf0a1e","referenced":"4379032b94fd48564b6b46f03d4a9fe6"}]}java.lang.NumberFormatException: For input string: "null"at java.lang.NumberFormatException.forInputString(NumberFormatException.java:65)at java.lang.Integer.parseInt(Integer.java:580)at java.lang.Integer.parseInt(Integer.java:615)at com.snc.cmdb.identify_reconcile.CIProcessor.getCompressedRecord(CIProcessor.java:447)at com.snc.cmdb.identify_reconcile.IndependentCIProcessor.getMatchingIndependentCI(IndependentCIProcessor.java:316)at com.snc.cmdb.identify_reconcile.IndependentCIProcessor.processRecord(IndependentCIProcessor.java:98)at com.snc.cmdb.identify_reconcile.CIProcessor.process(CIProcessor.java:103)..........................This is impacting the data import and import is getting failed.CauseThe number pointer exception is caused because the system tries to look for parsing an integer but there exists no value for the impacted record.In the current case, the issue is caused because of the empty sys_mod_count value of a CI record. The details of such records can be found using a DB query or below the same script. var mod = new GlideRecord('cmdb_ci');var count=0;mod.addEncodedQuery('sys_mod_count=NULL');//mod.setLimit(10);mod.query();while(mod.next()){//gs.log("Record sys ID "+ mod.sys_id);count++}gs.print("Total Record "+ count); This script can print all such sys_id's of the record and can also give the count of all records where sys_mod_count is empty.Sometimes, we may or may not find the exact record in CMDB because of a corrupt table or incorrect deletion. For example, in the below case, when we tried to search with one of the sys_id from the output, we could see the records getting listed in the list view but while open it shows record not found. --This is just one use case.In most of the use cases, you may find/open impacted records but the Mod Count might be empty. List View Form View: ResolutionIn order to resolve the issue, the below approaches can be followed: If the records are available in the system and can be opened using script - those records can be modified so that the sys_mod_count value will be populated.If the records corrupt (like one of the use cases above_ then using table cleaner or from the backend DB end, those records can be deleted. The above sample script can be modified as per the requirement to update the records.