Schedule-To-Start Timeout period
There are two primary uses case of this timeout:
- Detect whether an individual Worker has crashed.
- Detect whether the fleet of Workers polling the Task Queue is not able to keep up with the rate of Activity Tasks.
The default Schedule-To-Start Timeout is ∞ (infinity).
If this timeout is used, we recommend setting this timeout to the maximum time a Workflow Execution is willing to wait for an Activity Execution in the presence of all possible Worker outages, and have a concrete plan in place to reroute Activity Tasks to a different Task Queue. This timeout does not trigger any retries regardless of the Retry Policy, as a retry would place the Activity Task back into the same Task Queue. As a reminder, we do not recommend using this timeout unless you know what you are doing.
In most cases, we recommend monitoring the
temporal_activity_schedule_to_start_latency metric to know when Workers are not picking up Activity Tasks, instead of setting this timeout.