How to resolve SuccessFactors integration error: InvalidPathException could not find path in streamIssue <!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: #000000; } span { font-size: 12pt; font-family: Lato; color: #000000; } h2 { font-size: 24pt; font-family: Lato; color: black; } h3 { font-size: 18pt; font-family: Lato; color: black; } h4 { font-size: 14pt; font-family: Lato; color: black; } a { font-size: 12pt; font-family: Lato; color: #00718F; } a:hover { font-size: 12pt; color: #024F69; } a:target { font-size: 12pt; color: #032D42; } a:visited { font-size: 12pt; color: #00718f; } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } Resolve an InvalidPathException error that occurs when the SAM - Refresh SuccessFactors Integration Subscriptions scheduled job fails to download user subscriptions. The following error appears in the system logs: 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) The REST call returns a 400 error with the following response: {"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."}}} Example of the 400 error returned by the REST call: Release<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: #000000; } span { font-size: 12pt; font-family: Lato; color: #000000; } h2 { font-size: 24pt; font-family: Lato; color: black; } h3 { font-size: 18pt; font-family: Lato; color: black; } h4 { font-size: 14pt; font-family: Lato; color: black; } a { font-size: 12pt; font-family: Lato; color: #00718F; } a:hover { font-size: 12pt; color: #024F69; } a:target { font-size: 12pt; color: #032D42; } a:visited { font-size: 12pt; color: #00718f; } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } Quebec Cause<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: #000000; } span { font-size: 12pt; font-family: Lato; color: #000000; } h2 { font-size: 24pt; font-family: Lato; color: black; } h3 { font-size: 18pt; font-family: Lato; color: black; } h4 { font-size: 14pt; font-family: Lato; color: black; } a { font-size: 12pt; font-family: Lato; color: #00718F; } a:hover { font-size: 12pt; color: #024F69; } a:target { font-size: 12pt; color: #032D42; } a:visited { font-size: 12pt; color: #00718f; } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } This error occurs when a property referenced in the integration query is not configured in SuccessFactors. In this case, the "city" property is missing or not available in the SuccessFactors OData API configuration. Resolution<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: #000000; } span { font-size: 12pt; font-family: Lato; color: #000000; } h2 { font-size: 24pt; font-family: Lato; color: black; } h3 { font-size: 18pt; font-family: Lato; color: black; } h4 { font-size: 14pt; font-family: Lato; color: black; } a { font-size: 12pt; font-family: Lato; color: #00718F; } a:hover { font-size: 12pt; color: #024F69; } a:target { font-size: 12pt; color: #032D42; } a:visited { font-size: 12pt; color: #00718f; } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } Option 1: Configure the missing property in SuccessFactors Contact your SuccessFactors administrator to verify that the "city" property is configured and available in the OData API Data Dictionary. Option 2: Remove the missing property from the query If the city field is not required for your integration, remove it from the API call: Go to Flow Designer and open the SuccessFactors Download Subscriptions subflow.Open the Look up Users datastream action.In the Query Parameters field, locate the query string:userId,username,defaultFullName,firstName,lastName,gender,email,state,city,nationality,country,businessPhone,status,timeZone,title,hireDate,dateOfBirth,zipCodeRemove city from the query. The updated query should be:userId,username,defaultFullName,firstName,lastName,gender,email,state,nationality,country,businessPhone,status,timeZone,title,hireDate,dateOfBirth,zipCodeSelect Save, then select Publish. Run the scheduled job SAM - Refresh SuccessFactors Integration Subscriptions. To revert changes If you need to revert this modification: Go to the Update Versions [sys_update_version] table.Find the record for the modified Look up Users action.Revert to the Store Application: SuccessFactors Spoke update set.