3277842 - Performance degradation in CPI iFlows post Virginia MS Azure (DC68) migration - SAP SuccessFactors

Performance degradation seen in CPI iFlows with SuccessFactors post DC4 to Virginia MS Azure (DC68) migration for Next Generation Cloud Delivery.

SAP SuccessFactors HCM Suite

This is a known issue in SuccessFactors Virginia MS Azure (DC68) data center and the impacted customers are currently working with SAP's project team for the long term solution. 

Resolution and Workarounds (historical):
Edit your respective CPI workflows and replace the api4.*.com with either the cpi68preview.sapsf.com [20.106.118.218] for Preview or cpi68.successfactors.com [20.150.155.234] for Production. 


Should the above not work, where possible try the following workarounds:

1. Ask any downstream systems to increase the timeout, 
2. Delete the content enrichers and re-create the iflows, or
3. Our CPI/BTP team can assist in provisioning a new tenant in the respective data center from US West to US East (so  from <US2> to <US1>). Please note the existing SAP Cloud Integration tenant would not be migrated to a new region, instead a new tenant will be provisioned in the requested region US1).
Please note that the data migrations and all other configurations are to be done by the customer within 30 days.
SAP will not be able to extend this timeline due to security measurements and the old tenant will be decommissioned after 30 days.
If you wish to proceed with the migration, please create a new subaccount in the new region. Please make sure that this new subaccount is created within the same global account as the tenant to be migrated.
Once the new subaccount is created, provide Support with its details so that we can proceed with the tenant provisioning (Support component LOD-HCI-PI-OPS-PROV).

CPI,DC68,DC4,hyperscaler,NGCD,iFlow,performance,poor,slowness, latency,degradation , KBA , LOD-SF-INT-CPI , Standard SF to 3rd Party CPI (HCI) Content , Problem