{wip} update run task timeout

glennsarti · glennsarti · commit 55bf49174e42 · 2025-06-11T10:08:09.000+08:00
diff --git a/content/terraform-docs-common/docs/cloud-docs/api-docs/run-tasks/run-tasks-integration.mdx b/content/terraform-docs-common/docs/cloud-docs/api-docs/run-tasks/run-tasks-integration.mdx
@@ -135,10 +135,12 @@ The POST request submits the following properties as the request headers.
 
 ## Run Task Callback
 
-While a run task runs, it may send progressive updates to HCP Terraform with a `running` status. Once an integrator determines that Terraform supports detailed run task outcomes, they can send these outcomes by appending to the run task's callback payload.
+While a run task runs, it should send progressive updates to HCP Terraform with a `running` status.
+Once an integrator determines that Terraform supports detailed run task outcomes, they can send these outcomes by appending to the run task's callback payload.
 
-Once the external integration fulfills the request, that integration must call back into HCP Terraform with the overall result of either `passed` or `failed`. Terraform expects this callback within 10 minutes, or the request is considered errored.
+-> **Note:** HCP Terraform will consider the request as errored if it has not received a progress update in the last 10 minutes, or the request has been running for over 60 minutes.
 
+Once the external integration fulfills the request, that integration must call back into HCP Terraform with the overall result of either `passed` or `failed`.
 You can send outcomes with a status of `running`, `passed`, or `failed`, but it is a good practice only to send outcomes when a run task is `running`.
 
 `PATCH :callback_url`
diff --git a/content/terraform-docs-common/docs/cloud-docs/integrations/run-tasks/index.mdx b/content/terraform-docs-common/docs/cloud-docs/integrations/run-tasks/index.mdx
@@ -77,7 +77,8 @@ Once your server receives this payload, HCP Terraform expects you to callback to
 }
 ```
 
-HCP Terraform expects this callback within 10 minutes, or the task will be considered to have `errored`. The supplied message attribute will be displayed in HCP Terraform on the run details page. The status can be `running`, `passed` or `failed`.
+HCP Terraform will consider the request as errored if it has not received a progress callback in the last 10 minutes, or the task has been running for over 60 minutes.
+The supplied message attribute will be displayed in HCP Terraform on the run details page. The status can be `running`, `passed` or `failed`.
 
 Here's what the data flow looks like:
 

Original file line number	Diff line number	Diff line change
`@@ -77,7 +77,8 @@ Once your server receives this payload, HCP Terraform expects you to callback to`
`77`	`77`	`}`
`78`	`78`	```
`79`	`79`
`80`		-HCP Terraform expects this callback within 10 minutes, or the task will be considered to have `errored`. The supplied message attribute will be displayed in HCP Terraform on the run details page. The status can be `running`, `passed` or `failed`.
	`80`	`+HCP Terraform will consider the request as errored if it has not received a progress callback in the last 10 minutes, or the task has been running for over 60 minutes.`
	`81`	+The supplied message attribute will be displayed in HCP Terraform on the run details page. The status can be `running`, `passed` or `failed`.
`81`	`82`
`82`	`83`	`Here's what the data flow looks like:`
`83`	`84`