Successfactor- ServiceNow integration - Caught exception while parsing responseIssue Customer integrated ServiceNow with SuccessFactors as described under product documentation. However they are seeing an issue where out of 410 active users from SuccessFactors, ServiceNow is able to fetch only 184 users. When we click on the scheduled Job- >execute now ->We can see that Pull ToDos is failing with exception : "Caught exception while parsing response." Following the logs, we found the below errors in logs :2020-05-22 00:47:03 (764) worker.4 worker.4 txid=f90edcf31bb0 [0:00:00.002] Compacting large row block (file.write: wf_history 0 rows 0 saveSize)2020-05-22 00:47:03 (912) worker.4 worker.4 txid=f90edcf31bb0 WARNING *** WARNING *** Evaluator: java.lang.NullPointerException2020-05-22 00:47:04 (495) worker.4 worker.4 txid=******sn_hr_integrations (in the schedule record): ReturnResponse after processing the response from outbound connector {"status":-1,"errorReason":"Caught exception while parsing response.","error":"500","job_id":"********","external_source_id":"1c26e9dec3100300a669*****","hr_integration_service_id":"*******"} Cause{todo_filter_cond} is removed from the endpoint in - https://******.service-now.com/sys_rest_message_fn.do?sys_id=d580c7f50f043300dbc*******&sysparm_record_target=sys_rest_message_fn&sysparm_record_row=8&sysparm_record_rows=8&sysparm_record_list=rest_message%3De24cf9c5c3b0030079******* We have to use this filter condition to fetch ONLY the information that we need. OOB, we added conditions like - "&$filter=(categoryId ne '57' and categoryId ne '59') and (status eq '2' or status eq '3') and userNav/userId ne 'null'&$select=todoEntryId,todoEntryName,categoryLabel,dueDate,linkUrl,status,userNav/userId"This does not only filter the records but also fetches limited column information that we need. As this is removed in the instance, SF is sending a lot of information and flow is erroring out. ResolutionIssue is resolved by adding the parameter in the end point.