When submitting a process for execution through AWI's REST API the earliest start time AE uses UTC.
Example:
"execution_date_time": "2023-04-13T10:30:00Z"
Came into the queue with the earliest start time of 6:30:00am and since it was about 10 am when submitted, it ran immediately.
Release : 21.0.5
The previous behavior in v12.3 is wrong.
When sending an execute once rest request, the time must also be specified.
From the examples, a sample JSON would look like this:
{ "execution_date_time": "2018-02-27T10:00:00Z", "wait_for_manual_release": "false", "use_logical_time": "2018-02-27T10:00:00Z" },
The time is specified as "2018-02-27T10:00:00Z".
Notice the Z at the end.
According to the ISO 8601 standard, a Z at the end would explicitly mean UTC time.
The 12.3 version mistakenly converted it to local client time, whereas version 21 takes the input time as UTC.
The REST endpoint in v21 only supports time in specified in UTC, it is by design.
Nevertheless, if you want to execute an object with a specific Timezone, then you should pass it in via the property timezone to the REST API, example:
{
"object_name": "OBJECT_NAME",
"alias": "ALIAS_OBJECT",
"timezone":"TZ.CET",
"execution_option": "once",
"once":
{
"execution_date_time": "2024-02-27T08:36:57Z",
"wait_for_manual_release": "false",
"use_logical_time": "2024-02-27T08:36:57Z"
},
The REST API documentation will be improved in the future via AE-36385 to add more complete examples with all accepted parameters and how to use correctly the time parameters.