SAP Knowledge Base Article - Public

3732989 - Sent delta token was too old, initial load needed to retrieve states [Error 409] - SAP MDI

Symptom

During the replication process from MDI to SuccessFactors, the Business Scenario fails with the following error message: 'Error response code 409'

While checking the payloads, the following error message is seen: 'Sent delta token was too old, initial load needed to retrieve states'

Environment

  • SAP SuccessFactors
  • SAP Master Data Integration

Cause

A Delta Token is generated and returned to SuccessFactors after every successful execution. This token remains valid for 28 days: System Limitations.

  • Healthy State: If the integration runs successfully at least once every 28 days, the token is refreshed, and the cycle continues.
  • Failure State: If no successful execution occurs within 28 days, the token expires, and the integration can no longer perform incremental updates.

Resolution

Depending on whether you are working with a single configuration or multiple versions, follow the appropriate resolution path below:

###Scenario A: Standard Expiration (No Successful Execution)

The integration has been idle or failing for more than 28 days, but there are no versioning changes.

Resolution

  1. Navigate to Business Scenario Cost Center Replication from SAP Master Data Integration to EC.
  2. Perform a Manual Execution with the Delta Token as INITIAL.
  3. Once the execution completes successfully, MDI will provide a new, valid Delta Token to SuccessFactors, and the 28-day timer will reset.

###Scenario B: Versioning Conflict (Expired Token + Scheduled Old Version)

A new configuration version was created and saved, but a previous version remains scheduled in the background using an expired token.

Resolution

  1. Access the Business Scenario Cost Center Replication.
  2. Select the current/active version (the configuration intended for use that is not failing when triggering).
  3. Go to the 'Scheduling' tab.
  4. Define your desired schedule and Save.
  5. Why this works: Re-saving the schedule on the active version forces the background scheduler to drop the jobs associated with any previous versions. This stops the "phantom" executions that are still trying to use the invalid Delta Token from the old version.

See Also

Keywords

SAP Master Data Integration, MDI, SuccessFactors, Employee Central, EC, Error 409, "Sent delta token was too old", "initial load needed to retrieve states", Delta Token, Delta Token Expiration, 28-day rule, token lifecycle, versioning conflict, scheduling, Cost Center Replication, Business Scenario, manual execution, initial load, background jobs , KBA , LOD-SF-INT-MDI , OneMDI Business Scenarios , Problem

Product

SAP SuccessFactors HCM Core 2505