Functions and Assets API date_created and date_updated timestamps will be corrected
On September 1, 2026, date_created and date_updated fields in Functions and Assets resources will be corrected to return accurate UTC timestamps instead of values shifted forward by 7 hours. The fix applies retroactively to all resources, and customers using these fields for sorting, filtering, or comparisons should review their implementations before the correction date.
On September 1, 2026, date_created and date_updated on Functions and Assets resources will be updated to return accurate UTC timestamps.
Currently, these fields return values shifted forward by the Pacific Standard Time time zone offset (+7 hours) despite the Z suffix indicating UTC. This is a presentation-layer bug introduced in 2023; the underlying data is correct.
The correction applies retroactively. Any request made on or after September 1 will return corrected UTC values, including for resources created before that date.
What do you need to do?
Customers whose integrations depend on date_created or date_updated for sorting, filtering, display, time-range comparisons, or audit logic should review their implementation before September 1 to confirm it handles the corrected values.
This resource will help:
Source: original entry ↗