SAP Knowledge Base Article - Public

2739734 - Enabling session re-use is must when using "paging=snapshot"

Symptom

  • You have enabled server side pagination by using the parameter "paging=snapshot" in Successfactors OData API call
  • The first page is working fine and returning the response, the second page threw "500 internal server error"

For Example:

https://<api_url>/odata/v2/<Entity_Name>?$format=JSON&$paging=snapshot

Environment

Successfactors

Cause

Snapshot are created in local server, when Load Balancer switches server during pagination process, original snapshot will not be found in new server where the request is hit, thus will throw error and not recreate snapshot automatically, need to re-launch pagination process from 1st page and recreate snapshot in new server.

Resolution

  • When we use snapshot-based pagination, we must use long session to keep whole pagination process all in one same sever.
  • Session Re-use is must when using snapshot based pagination

How to enable session Re-use?

Reference Guide: https://help.sap.com/viewer/d599f15995d348a1b45ba5603e2aba9b/latest/en-US/335b30157cf5402f81697594962d6b6c.html

Keywords

snapshot pagination is not working , snapshot pagination returns error ,  successfactors odata api error , 500 internal server error , LOD-SF-INT-ODATA , LOD-SF-INT , KBA , LOD-SF-INT-ODATA , OData API Framework , LOD-SF-INT , SF Integrations - EC Payroll, Boomi/ HCI, API , Problem

Product

SAP SuccessFactors HCM Core 1811