SAP Knowledge Base Article - Public

2625431 - Error "Illegal instant due to time zone offset transition" is occurring in Integration Center or OData API

Symptom

The errors below are occurring:

Integration Center
"Cannot parse "2020-03-29T02:00:10": Illegal instant due to time zone offset transition (Europe/Amsterdam)"

OData API
<code>ServerErrorException</code>
<message lang="en-US">Illegal instant due to time zone offset transition (daylight savings time 'gap'): 2021-10-03T02:00:00.000 (Australia/Sydney)</message>

Image/data in this KBA is from SAP internal systems, sample data, or demo systems. Any resemblance to real data is purely coincidental.

Environment

  • SuccessFactors HXM Suite
    • Integration Center
    • OData API

Cause

The date being received by the API does not exist due to the Daylight Saving Time of the specific region which is mentioned in the error message (for example "Australia/Sydney" or "Europe/Amsterdam").

When Daylight Saving Time occurs, the time moves forward one hour. For example: Daylight Saving Time on Sydney started on Sunday, 3 October 2021. At 02:00 AM, the clocks were turned forward 1 hour, meaning that 02:00 AM became 03:00 AM. If the API receives a date value equal to 02:10 AM for example, it will fail because 02:00 interval AM doesn't exist as it was skipped by the Daylight Saving Time.

Resolution

The solution is to provide a date value that wouldn't be the one which was skipped by the Daylight Saving Time.

Keywords

time zone, offset, (Europe/Amsterdam), Illegal, instant, Day, Light, Savings, Timezone, Date, Change, Daylight, Saving, Time, ic, , KBA , LOD-SF-INT-ODATA , OData API Framework , LOD-SF-INT , Integrations , LOD-SF-INT-INC-ODATA , ODATA API In Integration Center , Problem

Product

SAP SuccessFactors HXM Suite all versions