The customer API sends timestamps without a time zone, but your workflow depends on daily cutoffs. How would you handle them?

Instruction: Distinguish event instants, local business times and dates. Explain who owns the cutoff rule and what happens when a timestamp cannot be interpreted uniquely.

Context: Tests business-time semantics, daylight-saving edge cases and an honest migration plan for ambiguous historical data.

Updated

Official answer available

Read the opening below, then unlock the full answer and practical guidance.

I’d ask the customer what those timestamps mean before converting them. They might represent an actual event instant, a local business time or a reporting date. I’d identify the source system’s time zone, the location that owns the cutoff and whether the cutoff uses event time or arrival time...

Upgrade to view official answer

Related Questions