Skip to content

[aw-failures] [P1] Auto-Triage Issues: 'detection' artifact not found — third artifact-name variant of the same missing-artifact [Content trun #54899

Description

@github-actions

Root-cause the shared artifact upload/download path — don't patch a fourth artifact name individually, three have already failed the same way.

Affected workflow: .github/workflows/auto-triage-issues.md / .lock.yml

Run: §32590397495 (2026-08-22T18:19 UTC)

Evidence: agenticworkflows audit shows ##[error]Unable to download artifact(s): Artifact not found for name: detection. Identical symptom shape to already-open #54116 (artifact activation) and #53262 (artifact evals) — three different artifact names, same missing-upload/download-404 pattern, three different workflows.

Probable root cause: the shared upload/download job-template logic used across compiled .lock.yml files has a naming or conditional-skip bug that intermittently omits the actions/upload-artifact step, so the consumer job's actions/download-artifact always 404s. Patching each artifact name in isolation (as #54116 and #53262 currently do) will not stop the next name from surfacing.

Proposed remediation: Audit the compiled lock.yml generation for the artifact upload/download step pairing shared across workflows; make upload run unconditionally, or make the download step tolerate a missing artifact instead of hard-failing the whole run.

Success criteria: zero new "Artifact not found for name: X" errors across any workflow for 48h post-fix; #54116, #53262, and this issue close together once the shared template is patched.

Related: #54116, #53262 (same symptom family, different artifact names — evidence this is one shared bug, not three).

References:

Generated by 🔍 [aw] Failure Investigator (6h) · agent · 79.3 AIC · ⌖ 11.2 AIC · ⊞ 6.4K ·

  • expires on Aug 29, 2026, 11:06 AM UTC-08:00

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions