In addition to the configuration level and the execution level, you can now set a
timeout parameter in the trigger level of a Job task.
A timeout set on a trigger applies on the task run started by this trigger only. It overrides the task configuration timeout if that task has one.
Set this timeout when you append a trigger to a schedule or update a trigger of that schedule:
- Append a trigger:
POSTat /orchestration/schedules/<scheduleId>/triggers - Update a trigger:
PUTat /orchestration/schedules/<scheduleId>/triggers
Note: When you set a timeout value on triggers, be aware
that
- Only time-based triggers support it; a webhook trigger does not.
- Its accuracy is 10 seconds.
- It is defined in minutes.
- It applies only on Job tasks running on Remote Engine Gen1 v2.12.0 and onwards, Remote Engine Cluster and Cloud Engine.