Execution Schedule
Last updated
Last updated
The execution schedule allows you to specify when and how a request should be executed.
Execution Schedule
executeAt
The date when the request should be executed.
executeIn
The time in milliseconds after which the request should be executed.
executeUntil
The maximum date when the request should be executed (for AT_EASE and PRIORITIZED priorities).
The executeAt property specifies the exact date and time for the request execution.
This property enables the definition of a desired date for request execution. It proves beneficial when expecting a delayed execution. However, the actual execution date may also depend on the request priority. In instances where the is not INSTANT, delays may occur based on the system load.
❗️Note: In case when Date is invalid or less then now the request will ignore this proprty.
The executeIn property specifies the time delay, in milliseconds, after which the request should be executed. In scenarios where execution is expected within hours or minutes, you can utilize this alternative field.
The executeUntil property defines the maximum date and time for request execution, particularly relevant for AT_EASE and PRIORITIZED priorities.
❗️Note: In cases when the Date provided is't compatible with request priority the field will be ignored. For example, if the priority is AT_EASE and date is 1 minute ahead -> the default behavior of AT_EASE will be used.