set-task-timeout

To prevent premature session timeouts for long-running browser automations, you can adjust the task-level timeout policy for the current session. This updates the progress timeout threshold without altering global defaults, ensuring steady progress is not misidentified as inactivity.

Your long-running model computation gets terminated because default idle thresholds are exceeded despite steady progress. You can avoid this by setting a higher progress_timeout_seconds for the current session, overriding aggressive timeout detection without changing global configurations.

To adjust task timeout settings for multi-step data processing without changing global defaults, apply a session-scoped timeout policy update. You must provide progress_timeout_seconds and a reason, with an optional hard_timeout_seconds to cap maximum duration.

You can set a hard timeout limit for extended model computations by providing the optional hard_timeout_seconds parameter. This caps the maximum duration while the required progress_timeout_seconds parameter prevents premature termination from idle threshold triggers.

The best way to manage timeout policies for large file processing is using a session-scoped timeout control. This requires a reason and progress_timeout_seconds to update only the current task's policy, preventing premature termination while leaving global defaults untouched.

You must provide a concise reason when updating the progress timeout for a current session. This reason documents why the long-running operation requires adjusted timeout settings, ensuring policy changes for progress_timeout_seconds are explicitly justified.