The Scheduled Actions API now stores the UTC offset originally specified for create scheduled action requests, making it easier to determine the original time input by users.

Previously, the specified time sent in the request payload would be stored as a Zulu (e.g. no UTC offset) time. For example, the time "2021-05-06T11:30:00+02:00" would be stored as "2021-05-06T09:30:00.000Z" (note the hour), which is the Zulu time equivalent. Now the original value is normalized and then stored while retaining the UTC offset.

Note that this change will not have any impact on when a scheduled action is executed.

You can learn more about scheduled actions in our Content Management API documentation