Findings
1. Repeated agent job failure before agent execution due to empty UV_PATH symlink target
Evidence:
/tmp/gh-aw/errors.json reports the same failing snippet in multiple runs:
ln: failed to create symbolic link '/opt/hostedtoolcache/gh-aw-tools/current/x64/bin/uv' -> '': No such file or directory- Immediately followed by
##[error]Process completed with exit code 1.
- Example runs from the last 7 days:
- In the same snippets,
UV_PATH: is empty before the failing ln command.
Affected runs/workflows:
- Observed repeatedly across
Trigger Code Complexity Detector and Trigger Code Duplication Detector failed runs in the lookback window.
Root cause context observed in logs:
- Failure occurs during the agent job setup sequence around
astral-sh/setup-uv, before normal agent task execution.
2. Cascade failures in conclusion phase caused by missing detection artifacts
Evidence:
/tmp/gh-aw/errors.json repeatedly shows:
##[error]Unable to download artifact(s): Artifact not found for name: <id>-detection
- Example runs (same lookback window):
Affected runs/workflows:
- Repeats in the conclusion job for failed detector workflows where detection output artifact is expected.
Root cause context observed in logs:
- Detection stage is marked skipped/failed in snippets (
RUN_DETECTION: false, DETECTION_AGENTIC_EXECUTION_OUTCOME: skipped), then conclusion tries to download a non-existent detection artifact.
3. Optional detection tool absent in runtime (warning pattern)
Evidence:
/tmp/gh-aw/errors.json contains repeated warning in detection job snippets:
##[warning]threat-detect binary not found on PATH; continuing because GH_AW_DETECTION_CONTINUE_ON_ERROR != false
- Seen in the same failed detector runs listed above.
Affected runs/workflows:
- Repeated in detector workflows where detection step executes with continue-on-error behavior.
Root cause context observed in logs:
- Runtime does not provide
threat-detect, and workflow policy explicitly allows continuing.
Per-repository run summary (last 7 days)
Window: 2026-08-25 to 2026-09-01 (UTC)
| Repository |
Scope |
Total runs |
Success |
Failure |
Other conclusions |
Failure rate |
elastic/ai-github-actions |
Failed-run metadata provided in /tmp/gh-aw/failed_runs.json |
20 |
0 |
20 |
0 |
100% |
Downstream repositories using these workflows were not established in this run context because authenticated bulk gh api repository/run enumeration was unavailable here; therefore only repository-local failed-run metadata from provided artifacts is included.
Generated by Internal: Agent Efficiency · copilot · gpt53codex · 13.7 AIC · ⌖ 5.5 AIC · ⊞ 29.9K · ◷
Findings
1. Repeated agent job failure before agent execution due to empty
UV_PATHsymlink targetEvidence:
/tmp/gh-aw/errors.jsonreports the same failing snippet in multiple runs:ln: failed to create symbolic link '/opt/hostedtoolcache/gh-aw-tools/current/x64/bin/uv' -> '': No such file or directory##[error]Process completed with exit code 1.trigger-code-complexity-detector.yml)trigger-code-duplication-detector.yml)trigger-code-complexity-detector.yml)trigger-code-duplication-detector.yml)UV_PATH:is empty before the failinglncommand.Affected runs/workflows:
Trigger Code Complexity DetectorandTrigger Code Duplication Detectorfailed runs in the lookback window.Root cause context observed in logs:
astral-sh/setup-uv, before normal agent task execution.2. Cascade failures in conclusion phase caused by missing detection artifacts
Evidence:
/tmp/gh-aw/errors.jsonrepeatedly shows:##[error]Unable to download artifact(s): Artifact not found for name: <id>-detectionAffected runs/workflows:
Root cause context observed in logs:
RUN_DETECTION: false,DETECTION_AGENTIC_EXECUTION_OUTCOME: skipped), then conclusion tries to download a non-existent detection artifact.3. Optional detection tool absent in runtime (warning pattern)
Evidence:
/tmp/gh-aw/errors.jsoncontains repeated warning in detection job snippets:##[warning]threat-detect binary not found on PATH; continuing because GH_AW_DETECTION_CONTINUE_ON_ERROR != falseAffected runs/workflows:
Root cause context observed in logs:
threat-detect, and workflow policy explicitly allows continuing.Per-repository run summary (last 7 days)
Window: 2026-08-25 to 2026-09-01 (UTC)
elastic/ai-github-actions/tmp/gh-aw/failed_runs.jsonDownstream repositories using these workflows were not established in this run context because authenticated bulk
gh apirepository/run enumeration was unavailable here; therefore only repository-local failed-run metadata from provided artifacts is included.