Symptom
This KBA collects common error during using Clock In Clock Out Time Events related API.
Environment
SAP SuccessFactors Time Tracking
Resolution
- Scenario 1: When using REST API to import Terminal Time Events to SF, receive Response with HTTP Status 500 Internal Server Error "A time event for this employee and timestamp already exists."
Resolution1: All the time events in the request payload are incorrect. None of the time events are saved because of the duplicate timestamp and assignment ID, or something is wrong at the server-side.
If at least one of the time events were saved, the response would be with HTTPS Status 201 Created. - Scenario 2: When using REST API to import Terminal Time Events to SF, receive Response with HTTP Status 400 Bad Request: Validation Error.
Resolution 2: Any of the values incorrectly mentioned for the Requested Payload. For example, in request payload The assignment id is 'cgrant--'.
The assignment id must not contain special characters, the correct assignmentid should be 'cgrant'.
See Also
SAP Support Portal Documentation: REST API for Sending Time Events from Terminal to Clock In Clock Out
Keywords
Clock In Clock Out, REST API error, time events import, 500 Internal Server Error, "A time event for this employee and timestamp already exists", validation error , KBA , LOD-SF-TTR-CIO , Clock In/ Clock Out , How To
Product
SAP SuccessFactors Time Tracking all versions
SAP Knowledge Base Article - Public