GHA workflow cancelled

[ZePan110]

Select Topic Area

Question

Body

GHA workflow has been cancelled without reason. Does anyone know the reason for this?
It is known that the dependent job is executing normally, the workflow has not timed out, and there are no other users performing cancellation operations. So there was no prompt message cancelled. And we have set up 'fail-fast: false'
https://github.com/opea-project/GenAIExamples/actions/runs/14222501285/job/39895011148

[dpoliakov-tv]

i have the same situation.
i've read log file /actions-runners/runner_1/_diag/Worker-....log and noticed next:

1. we create wss connection to GH servers
2. we receive message about cancellation without any reason...

We use:

1. self-hosted-runner,
2. runner version is 2.323.0,
3. binary launched in docker container,
4. docker image is ubuntu-20.04

[2025-04-10 12:10:04Z INFO JobRunner] Initializing launch client
[2025-04-10 12:10:04Z INFO JobServerQueue] Initializing results client
[2025-04-10 12:10:04Z INFO ResultServer] Creating websocket client ...wss://results-receiver.actions.githubusercontent.com/_ws/ingest.sock
[2025-04-10 12:10:04Z INFO ResultServer] Attempting to start websocket client with delay 00:00:00.
[2025-04-10 12:10:04Z INFO JobServerQueue] Start process web console line queue.
[2025-04-10 12:10:04Z INFO JobServerQueue] Start process file upload queue.
[2025-04-10 12:10:04Z INFO JobServerQueue] Start results file upload queue.
[2025-04-10 12:10:04Z INFO JobServerQueue] Starting results-based upload queue...
[2025-04-10 12:10:04Z INFO JobServerQueue] Start process timeline update queue.
[2025-04-10 12:10:04Z INFO ExecutionContext] Initialize GitHub context
[2025-04-10 12:10:04Z INFO ExecutionContext] Initialize Env context
[2025-04-10 12:10:04Z INFO JobRunner] Starting the job execution context.
[2025-04-10 12:10:04Z INFO JobRunner] Getting job extension.
[2025-04-10 12:10:04Z INFO JobRunner] Initialize job. Getting all job steps.
[2025-04-10 12:10:04Z INFO PipelineDirectoryManager] Updating job run properties.
[2025-04-10 12:10:04Z INFO JobExtension] Downloading actions
[2025-04-10 12:10:04Z INFO ResultServer] Successfully started websocket client.
[2025-04-10 12:10:04Z INFO JobServerQueue] Try to append 1 batches web console lines for record '288e3f90-e054-49f9-bc92-4d653b0353a2', success rate: 1/1.
[2025-04-10 12:10:04Z INFO Worker] Listening for cancel message from the channel.
[2025-04-10 12:10:04Z INFO ProcessChannel] Receiving message of length 0, with hash 'e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855'
[2025-04-10 12:10:04Z INFO Worker] Waiting for the job to complete or for a cancel message from the channel.
[2025-04-10 12:10:04Z INFO Worker] Cancellation/Shutdown message received.
[2025-04-10 12:10:04Z WARN GitHubActionsService] POST request to https://launch.actions.githubusercontent.com/actions/build/f0f20270-85e6-4e45-8625-72084ccc140e/jobs/63462c69-02d8-52b7-b188-006427ec0d3d/runnerresolve/actions has been cancelled.

[2025-04-10 12:10:04Z ERR  JobExtension] Caught cancellation exception from JobExtension Initialization: System.Threading.Tasks.TaskCanceledException: A task was canceled.
 ---> System.Threading.Tasks.TaskCanceledException: A task was canceled.
   at System.Threading.Tasks.TaskCompletionSourceWithCancellation`1.WaitWithCancellationAsync(CancellationToken cancellationToken)
   at System.Net.Http.HttpConnectionPool.SendWithVersionDetectionAndRetryAsync(HttpRequestMessage request, Boolean async, Boolean doRequestAuth, CancellationToken cancellationToken)
   at System.Net.Http.AuthenticationHelper.SendWithAuthAsync(HttpRequestMessage request, Uri authUri, Boolean async, ICredentials credentials, Boolean preAuthenticate, Boolean isProxyAuth, Boolean doRequestAuth, HttpConnectionPool pool, CancellationToken cancellationToken)
   at System.Net.Http.RedirectHandler.SendAsync(HttpRequestMessage request, Boolean async, CancellationToken cancellationToken)
   at GitHub.Services.Common.RawHttpMessageHandler.SendAsync(HttpRequestMessage request, CancellationToken cancellationToken)
   at GitHub.Services.Common.VssHttpRetryMessageHandler.SendAsync(HttpRequestMessage request, CancellationToken cancellationToken)
   at System.Net.Http.HttpClient.<SendAsync>g__Core|83_0(HttpRequestMessage request, HttpCompletionOption completionOption, CancellationTokenSource cts, Boolean disposeCts, CancellationTokenSource pendingRequestsCts, CancellationToken originalCancellationToken)
   --- End of inner exception stack trace ---
   at System.Net.Http.HttpClient.HandleFailure(Exception e, Boolean telemetryStarted, HttpResponseMessage response, CancellationTokenSource cts, CancellationToken cancellationToken, CancellationTokenSource pendingRequestsCts)
   at System.Net.Http.HttpClient.<SendAsync>g__Core|83_0(HttpRequestMessage request, HttpCompletionOption completionOption, CancellationTokenSource cts, Boolean disposeCts, CancellationTokenSource pendingRequestsCts, CancellationToken originalCancellationToken)
   at Sdk.WebApi.WebApi.RawHttpClientBase.SendAsync(HttpRequestMessage message, HttpCompletionOption completionOption, Object userState, CancellationToken cancellationToken)
   at GitHub.Services.Launch.Client.LaunchHttpClient.GetLaunchSignedURLResponse[R,T](Uri uri, R request, CancellationToken cancellationToken)
   at GitHub.Services.Launch.Client.LaunchHttpClient.GetResolveActionsDownloadInfoAsync(Guid planId, Guid jobId, ActionReferenceList actionReferenceList, CancellationToken cancellationToken)
   at GitHub.Runner.Worker.ActionManager.GetDownloadInfoAsync(IExecutionContext executionContext, List`1 actions)
   at GitHub.Runner.Worker.ActionManager.PrepareActionsRecursiveAsync(IExecutionContext executionContext, PrepareActionsState state, IEnumerable`1 actions, Int32 depth, Guid parentStepId)
   at GitHub.Runner.Worker.ActionManager.PrepareActionsAsync(IExecutionContext executionContext, IEnumerable`1 steps, Guid rootStepId)
   at GitHub.Runner.Worker.JobExtension.InitializeJob(IExecutionContext jobContext, AgentJobRequestMessage message)
[2025-04-10 12:10:04Z INFO ExecutionContext] Publish step telemetry for current step {
  "action": "setup_job",
  "type": "runner",
  "stage": "Pre",
  "stepId": "288e3f90-e054-49f9-bc92-4d653b0353a2",
  "result": "canceled",
  "errorMessages": [
    "A task was canceled."
  ],
  "executionTimeInSeconds": 1,
  "startTime": "2025-04-10T12:10:04.4545343Z",
  "finishTime": "2025-04-10T12:10:04.7542843Z"
}.
[2025-04-10 12:10:04Z ERR  JobRunner] Job is cancelled during initialize.
[2025-04-10 12:10:04Z ERR  JobRunner] Caught exception: System.Threading.Tasks.TaskCanceledException: A task was canceled.
 ---> System.Threading.Tasks.TaskCanceledException: A task was canceled.
   at System.Threading.Tasks.TaskCompletionSourceWithCancellation`1.WaitWithCancellationAsync(CancellationToken cancellationToken)
   at System.Net.Http.HttpConnectionPool.SendWithVersionDetectionAndRetryAsync(HttpRequestMessage request, Boolean async, Boolean doRequestAuth, CancellationToken cancellationToken)
   at System.Net.Http.AuthenticationHelper.SendWithAuthAsync(HttpRequestMessage request, Uri authUri, Boolean async, ICredentials credentials, Boolean preAuthenticate, Boolean isProxyAuth, Boolean doRequestAuth, HttpConnectionPool pool, CancellationToken cancellationToken)
   at System.Net.Http.RedirectHandler.SendAsync(HttpRequestMessage request, Boolean async, CancellationToken cancellationToken)
   at GitHub.Services.Common.RawHttpMessageHandler.SendAsync(HttpRequestMessage request, CancellationToken cancellationToken)
   at GitHub.Services.Common.VssHttpRetryMessageHandler.SendAsync(HttpRequestMessage request, CancellationToken cancellationToken)
   at System.Net.Http.HttpClient.<SendAsync>g__Core|83_0(HttpRequestMessage request, HttpCompletionOption completionOption, CancellationTokenSource cts, Boolean disposeCts, CancellationTokenSource pendingRequestsCts, CancellationToken originalCancellationToken)
   --- End of inner exception stack trace ---
   at System.Net.Http.HttpClient.HandleFailure(Exception e, Boolean telemetryStarted, HttpResponseMessage response, CancellationTokenSource cts, CancellationToken cancellationToken, CancellationTokenSource pendingRequestsCts)
   at System.Net.Http.HttpClient.<SendAsync>g__Core|83_0(HttpRequestMessage request, HttpCompletionOption completionOption, CancellationTokenSource cts, Boolean disposeCts, CancellationTokenSource pendingRequestsCts, CancellationToken originalCancellationToken)
   at Sdk.WebApi.WebApi.RawHttpClientBase.SendAsync(HttpRequestMessage message, HttpCompletionOption completionOption, Object userState, CancellationToken cancellationToken)
   at GitHub.Services.Launch.Client.LaunchHttpClient.GetLaunchSignedURLResponse[R,T](Uri uri, R request, CancellationToken cancellationToken)
   at GitHub.Services.Launch.Client.LaunchHttpClient.GetResolveActionsDownloadInfoAsync(Guid planId, Guid jobId, ActionReferenceList actionReferenceList, CancellationToken cancellationToken)
   at GitHub.Runner.Worker.ActionManager.GetDownloadInfoAsync(IExecutionContext executionContext, List`1 actions)
   at GitHub.Runner.Worker.ActionManager.PrepareActionsRecursiveAsync(IExecutionContext executionContext, PrepareActionsState state, IEnumerable`1 actions, Int32 depth, Guid parentStepId)
   at GitHub.Runner.Worker.ActionManager.PrepareActionsAsync(IExecutionContext executionContext, IEnumerable`1 steps, Guid rootStepId)
   at GitHub.Runner.Worker.JobExtension.InitializeJob(IExecutionContext jobContext, AgentJobRequestMessage message)
   at GitHub.Runner.Worker.JobRunner.RunAsync(AgentJobRequestMessage message, CancellationToken jobRequestCancellationToken)
[2025-04-10 12:10:04Z INFO JobRunner] Shutting down the job server queue.
[2025-04-10 12:10:04Z INFO JobServerQueue] Fire signal to shutdown all queues.

[omer2500]

We’ve also observed this issue

Specifically, we’re able to consistently reproduce the problem when running a large number of parallel jobs. This further supports our suspicion that the issue may be related to system limits or resource contention under heavy workload.

[Noamshmueli]

We also faced this issue in self hosted runner

[github-actions[bot]]

🕒 Discussion Activity Reminder 🕒

This Discussion has been labeled as dormant by an automated system for having no activity in the last 60 days. Please consider one the following actions:

1️⃣ Close as Out of Date: If the topic is no longer relevant, close the Discussion as out of date at the bottom of the page.

2️⃣ Provide More Information: Share additional details or context — or let the community know if you've found a solution on your own.

3️⃣ Mark a Reply as Answer: If your question has been answered by a reply, mark the most helpful reply as the solution.

Note: This dormant notification will only apply to Discussions with the Question label. To learn more, see our recent announcement.

Thank you for helping bring this Discussion to a resolution! 💬

[AshimaSingh0610]

❓ Problem – Workflow Cancelled Without Any Reason
The GitHub Actions (GHA) workflow was suddenly cancelled.
There was no timeout, no manual cancellation, and fail-fast: false was already set — yet the job stopped right after starting.

���� Cause – What Likely Happened
The job was running on a self-hosted runner inside Docker, which might have hit resource or network limits.

The WebSocket connection to GitHub dropped, so GitHub assumed the runner was offline and auto-cancelled the job.

Too many parallel jobs were running, which caused load or delays.

A GitHub-side issue or action-fetch failure triggered a TaskCanceledException.

✅ Solution – What You Can Do
Run the runner outside Docker, or allocate more CPU/RAM.

Ensure stable internet/network — WebSocket shouldn’t drop.

Keep the runner version updated.

Limit or stagger parallel jobs to reduce load.

If it happens often, contact GitHub support with logs and job link.

🔧 One-line Summary:
"GitHub cancelled the job because the Docker runner hit a resource or connection issue. Try running it outside Docker or increase resources."

[github-actions[bot]]

🕒 Discussion Activity Reminder 🕒

This Discussion has been labeled as dormant by an automated system for having no activity in the last 60 days. Please consider one the following actions:

1️⃣ Close as Out of Date: If the topic is no longer relevant, close the Discussion as out of date at the bottom of the page.

2️⃣ Provide More Information: Share additional details or context — or let the community know if you've found a solution on your own.

3️⃣ Mark a Reply as Answer: If your question has been answered by a reply, mark the most helpful reply as the solution.

Note: This dormant notification will only apply to Discussions with the Question label. To learn more, see our recent announcement.

Thank you for helping bring this Discussion to a resolution! 💬