3723203 - Updates sent via Learning API do not update the desired users' records

Whenever an API is called to push updates to Learning users, the updates do not come through and Learning API fails for third party vendor.

SAP SuccessFactors Learning

In this situation, the issue may be related to the user ID used in the GET API that is not correct.

The issue found in Learning logs refer to the User ID incorrect in the GET API call. See the logs below:

2026-01-17T23:57:59.429 +0000 [INFO ] {JSESSION_ID=(no session), x-correlation-id=82d8765786222dc95257f0f613710fc2} - xxx - RequestLogger - GET - 3BFC18DF2D103CB3A2D322B4B7B68253 - https://<customer_prefix_url>/learning/odatav4/public/user/userlearning-service/v1/LearningHistories - status=500 - errorSummary=LMSODataApplicationException (Invalid Student ID.) | ElmsFinderException (Invalid Student ID.) | - internalErrorStatus=400

[17/Jan/2026:23:57:59 +0000] JSESSIONID:- Request:GET /learning/odatav4/public/user/userlearning-service/v1/LearningHistories?$filter=criteria/targetUserID%20eq%20'AXN0TRD' HTTP/1.1 - Status: 500 - Bytes: 55 x-correlation-id:82d8765786222dc95257f0f613710fc2

Vendor is responsible for building the API call with the correct details. Please approach them and validate what are the IDs they are using and check whether they match with the Learning User IDs.

odata, api, get, user, id, userlearning-service, LearningHistories, error, 400, 500, HTTP , KBA , LOD-SF-LMS-ODA , Web Services OData , LOD-SF-LMS-OCN , Open Content Network , Problem