GitHub Actions / GitHub Actions

GitHub Actions TempDirectoryManager Race Condition Wipes Active Worker Temp Directory

Fix GitHub Actions race condition where cancelled Worker deletes temp directory used by new Worker Includes evidence for GitHub Actions troubleshooting demand.

Source-backed Last updated May 14, 2026 1 source Needs local verification

Category: GitHub Actions
Error signature: TempDirectoryManager race condition: cancelled Worker wipes _temp directory used by concurrently spawned new Worker
Quick fix: Compare the failing environment with a known working setup, then change one configuration value at a time.
Updated: May 14, 2026
Verification status: Source-backed
Evidence: 1 public source URL

Before you change production

This page includes public source URLs in the imported troubleshooting record. Compare those references with your version and environment before applying changes.

Reproduce the smallest failing action and save non-secret logs before changing configuration.
Check versions for GitHub Actions, related SDKs, package managers, CI runners, and hosting providers.
Change one setting or dependency at a time, then rerun the same failing command or request.
Avoid destructive commands, credential rotation, billing changes, or security relaxations without a rollback plan.

What this error means

TempDirectoryManager race condition: cancelled Worker wipes _temp directory used by concurrently spawned new Worker is a GitHub Actions failure pattern reported for developers trying to fix github actions race condition where cancelled worker deletes temp directory used by new worker. Based on the imported evidence, treat this as a tool-specific troubleshooting page rather than a generic API error.

Why this happens

GitHub Actions runner shares _temp directory between old (cancelled) and new worker processes. Cancelled worker's TempDirectoryManager cleanup deletes files being used by the new worker, causing intermittent CI failures that are hard to reproduce.

Common causes

When GitHub Actions runner receives a new job while previous worker is still running, the cancelled worker's cleanup wipes the shared _temp directory, corrupting the new worker's environment. Causes mysterious CI failures.
GitHub Actions runner shares _temp directory between old (cancelled) and new worker processes. Cancelled worker's TempDirectoryManager cleanup deletes files being used by the new worker, causing intermittent CI failures that are hard to reproduce.

Quick fixes

Confirm the exact error signature matches TempDirectoryManager race condition: cancelled Worker wipes _temp directory used by concurrently spawned new Worker.
Check the GitHub Actions account, local tool state, and provider configuration involved in the failing workflow.
Compare the failing environment with a known working setup, then change one configuration value at a time.

Platform/tool-specific checks

Verify the command, editor, extension, or API client that produced the error.
Compare local settings with CI, deployment, or editor-level settings when the error appears in only one environment.
Avoid deleting credentials, local model data, or project settings until the failing scope is clear.

Step-by-step troubleshooting

Capture the exact error message and the command, editor action, or request that triggered it.
Check whether the failure is account/auth, quota/rate, model/provider, local runtime, or deployment configuration.
Review the source evidence below and compare it with your environment.
Apply one change at a time and rerun the smallest failing action.
Keep the working fix documented for the team or deployment environment.

How to prevent it

Keep provider/tool configuration documented.
Record non-secret diagnostics such as tool version, provider name, model name, and command path.
Add a lightweight check before CI or production workflows depend on the tool.

Diagnostic flow for this page

Match TempDirectoryManager race condition: cancelled Worker wipes _temp directory used by concurrently spawned new Worker exactly before applying the quick fix.
Compare the failing environment with GitHub Actions versions, account scope, provider settings, and deployment context.
Check the listed common causes in order, starting with the cause that best matches your logs.
Use the evidence status below to decide whether to confirm against public sources or official documentation.
Apply one reversible change, rerun the smallest failing action, and keep rollback notes.

FAQ

What does TempDirectoryManager race condition: cancelled Worker wipes _temp directory used by concurrently spawned new Worker mean in GitHub Actions?

TempDirectoryManager race condition: cancelled Worker wipes _temp directory used by concurrently spawned new Worker indicates the workflow described by "GitHub Actions TempDirectoryManager Race Condition Wipes Active Worker Temp Directory" failed in a GitHub Actions context. Start by confirming the exact signature and the component that emitted it.

What should I check first for TempDirectoryManager race condition: cancelled Worker wipes _temp directory used by concurrently spawned new Worker?

Check whether this cause matches your environment: When GitHub Actions runner receives a new job while previous worker is still running, the cancelled worker's cleanup wipes the shared _temp directory, corrupting the new worker's environment. Causes mysterious CI failures.

Is the TempDirectoryManager race condition: cancelled Worker wipes _temp directory used by concurrently spawned new Worker guidance source-backed?

The "GitHub Actions TempDirectoryManager Race Condition Wipes Active Worker Temp Directory" page is labeled source-backed. It has 1 public source URL from github.com, so use that evidence status when deciding how much additional verification you need.

When should I avoid the quick fix for TempDirectoryManager race condition: cancelled Worker wipes _temp directory used by concurrently spawned new Worker?

For "GitHub Actions TempDirectoryManager Race Condition Wipes Active Worker Temp Directory", avoid applying "Compare the failing environment with a known working setup, then change one configuration value at a time." when the error text differs, the affected version or provider is different, or the change would touch credentials, billing, DNS, production deploy settings, or irreversible data.

What should I collect before debugging TempDirectoryManager race condition: cancelled Worker wipes _temp directory used by concurrently spawned new Worker?

For "GitHub Actions TempDirectoryManager Race Condition Wipes Active Worker Temp Directory", collect the failing GitHub Actions command or request, non-secret configuration, versions, timestamps, request IDs when available, and the smallest reproduction that still triggers the signature.