From f49bb9a3f1cf9eccb12eca11fa36712c6b6f8e05 Mon Sep 17 00:00:00 2001 From: MTomBosch Date: Tue, 12 May 2026 10:58:01 +0200 Subject: [PATCH] Clarify cancellation process in workflow documentation --- .../reference/workflows-and-actions/workflow-cancellation.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/actions/reference/workflows-and-actions/workflow-cancellation.md b/content/actions/reference/workflows-and-actions/workflow-cancellation.md index 2930da0b38a7..c9a9a8092388 100644 --- a/content/actions/reference/workflows-and-actions/workflow-cancellation.md +++ b/content/actions/reference/workflows-and-actions/workflow-cancellation.md @@ -19,4 +19,4 @@ When canceling a workflow run, you may be running other software that uses resou 1. For jobs that need to be canceled, the server sends a cancellation message to all the runner machines with jobs that need to be canceled. 1. For jobs that continue to run, the server re-evaluates `if` conditions for the unfinished steps. If the condition evaluates to `true`, the step continues to run. You can use the `cancelled` expression to apply a status check of `cancelled()`. For more information, see [AUTOTITLE](/actions/reference/evaluate-expressions-in-workflows-and-actions#cancelled). 1. For steps that need to be canceled, the runner machine sends `SIGINT/Ctrl-C` to the step's entry process (`node` for JavaScript actions, `docker` for container actions, and `bash/cmd/pwd` when using `run` in a step). If the process doesn't exit within 7500 ms, the runner will send `SIGTERM/Ctrl-Break` to the process, then wait for 2500 ms for the process to exit. If the process is still running, the runner kills the process tree. -1. After the 5 minute cancellation timeout period, the server will forcibly terminate all jobs and steps that are still running. +1. After the 5 minute cancellation timeout period, the server will forcibly terminate all jobs (marked in step 1 to be canceled) and steps that are still running.