Success Factor Integration - failed with error: java.lang.RuntimeException: com.glide.transform.transformer.exceptions.InvalidPathException: Could not find path in stream: $.d.resultsIssue When the Scheduled Job "SAM - Refresh Success Factor Integration Subscriptions" job runs the SuccessFactors user subscriptions are not downloaded. The error is observed in the syslogs: Operation(Look up Users.page$1.f880df9453d62010f263ddeeff7b12eb) failed with error: java.lang.RuntimeException: com.glide.transform.transformer.exceptions.InvalidPathException: Could not find path in stream: $.d.resultsat com.glide.transform.transformer.TransformerResultIterator.getNextRow(TransformerResultIterator.java:50)at com.glide.transform.transformer.TransformerResultIterator.hasNext(TransformerResultIterator.java:65)at com.snc.process_flow.stream.SplittingDatastream.getNextRecord(SplittingDatastream.java:105)at com.snc.process_flow.stream.SplittingDatastream.hasNext(SplittingDatastream.java:90)at com.snc.process_flow.stream.ScriptParserStream.getCo(ScriptParserStream.java:127) Also, observed the following error in the Response body in the REST call which is causing the "400" error. Please see the attached screenshot "REST Call error.png".===={"error" : {"code" : "COE_PROPERTY_NOT_FOUND", "message" : {"lang" : "en-US", "value" : "[COE0021]Invalid property names: User/city. Please check the property name in Admin Center > OData API Data Dictionary or entity metadata. Ensure there were no data model changes that removed this field, and please execute a refresh metadata to ensure the cache is not corrupted."}}}==== ReleaseQuebecCauseThe issue is caused when the property is not set up or configured from the SuccessFactors. From the error above "Invalid property names: User/city", it is the "city" that is missing. ResolutionSolution: Please reach out to your SuccessFactors team to check on the "city" property and have it resolved. Workaround: 1. We have modified the "Look up Users" action from the Subflow "SuccessFactors Download Subscriptions".*** Removing the 'city' parameter from the API call in 'Look Up Users' datastream action. As this field is currently not used anywhere, it will not impact the Integration flow. Please see the screenshot attached "Look up Users - Flow Action.png". The query contains "userId,username,defaultFullName,firstName,lastName,gender,email,state,city,nationality,country,businessPhone,status,timeZone,title,hireDate,dateOfBirth,zipCode". a. We have removed the "city" from the Query Parameters. b. The query parameter now have the following:"userId,username,defaultFullName,firstName,lastName,gender,email,state,nationality,country,businessPhone,status,timeZone,title,hireDate,dateOfBirth,zipCode" 2. Save and Publish the Action. 3. Run the Scheduled Job "SAM - Refresh Success Factor Integration Subscriptions" Note: a. To revert the changes done, please navigate to the following record in 'sys_update_version' table. b. Find the related record that was changed. c. Revert back to the 'Store Application: SuccessFactors Spoke' update set.