Documentation of Workflow Task Timeout

On the documentation page Workflows | Temporal Documentation , under the sub section for Workflow Task Timeout, it says the following -
The default value is 10 seconds. This timeout is primarily available to recognize whether a Worker has gone down so that the Workflow Execution can be recovered on a different Worker. The main reason for increasing the default value would be to accommodate a Workflow Execution that has a very long Workflow Execution History that could take longer than 10 seconds for the Worker to load.

Why would a long workflow execution history cause worker to load late? The worker is remote to the temporal cluster and only ever does the next set of commands with a local state, but the history itself is maintained by the cluster. Wanted to understand this statement better…can you please provide some insight here…thanks

Hello @Himaja

As you have mentioned above, if a worker crashes the workflow execution is placed on a different worker. As part of the Workflow Task, the worker pulls the workflow history and replays the workflow execution in order to recreate the workflow state, and continues from there.

the history itself is maintained by the cluster

that is true, but it is also cached by the worker executing the workflow.

Thank you that helps