SFAPI and OData performance issues for API entity USER during upsert operation.
Successfactors BizX System
Reproducing the Issue
Open the Admin center > OData API Audit logs > find the User entity upserts with slow API response times like 5+ minutes
Open the Admin center > SFAPI Audit logs > find the User entity upserts with slow API response times like 5+ minutes
There can be several root cause for this performance issues:
- High load on API server when upsert request was triggered which can cause slowness.
- Upsert request contains Mangerial information or OData/SFAPI parameter which makes API calls to go through complex DB update logic.
- Types of Dynamic group or Role defined in SFSF system: API request would wait until all dynamic groups defined in SF system would get refreshed for all the user in that particular batch request.
To avoid performance issues, Support will follow steps mentioned in "Internal Memo" of this article.
However, customer approval is required to enable async mode in SF database. This would separate the API upsert and Dynamic Group refresh in database.
IMPORTANT: Enable Refresh Framework is enabled on all Datacenters from November 2019 - Only instances which are running Refresh RBP Rules jobs will not have the Enable refresh framework enabled by default
2766870 Role Based Permissions (RBP) Refresh Framework FAQ - SuccessFactors
User Upsert, Performance issue, RBP refresh, refresh RBP Rules, Refresh Framework, slow, timeout, PI, ERP, OData, SFAPI, API, SuccessFactors, Talent addon , KBA , LOD-SF-INT-API , API & Adhoc API Framework , LOD-SF-INT , Integrations , LOD-SF-INT-ODATA , OData API Framework , LOD-SF-INT-ADD , Talent Hybrid AddOn Solution , Problem