Skip to content

[aw-failures] Copilot/Codex runner: intermittent engine binary missing at startup (node/codex not found) #28726

Closed as not planned

Description

@github-actions

Two Copilot CLI workflows failed with node: command not found in a 1.5-hour burst on 2026-04-27, and one Codex workflow failed with codex: command not found in the same 6h window. Both failure modes share the same root cause: the engine binary was absent from PATH when the runner agent step launched, killing the workflow before any agent output was produced.

Affected Workflows

Workflow Engine Run Time (UTC) Error Auto-issue
Daily News Copilot CLI §24986870660 09:25 node: command not found #28681
Daily Issues Report Generator Copilot CLI §24990655972 10:53 node: command not found #28689
Daily Fact About gh-aw Codex §24992928191 11:41 codex: command not found #28703

Root Cause

Runner slot(s) provisioned without the engine binary in PATH during the 09:25–11:41 UTC window. The Copilot CLI is Node.js-based; when node is absent the CLI fails immediately at startup. The Codex binary is a separate installation that similarly was not found.

This is intermittent — other Copilot CLI runs (Auto-Triage Issues, PR Triage Agent, Visual Regression Checker, Smoke CI, Delight) and other Codex runs (AI Moderator ×2, Duplicate Code Detector) all succeeded in the same 6h window, confirming correct provisioning on most runner slots.

Proposed Remediation

  1. Verify that the runner setup action for each engine includes a post-setup node --version / codex --version health-check that fails fast with a clear diagnostic before the agent job starts.
  2. Add a setup-node step (or ensure actions/setup-node runs) in the Copilot CLI agent job to guarantee Node.js is in PATH before the CLI is invoked.
  3. Investigate whether a specific runner label or pool is responsible for slots that intermittently lack the required binary.

Success Criteria

Zero recurrence of command not found engine startup errors across 5+ consecutive scheduled runs of affected workflows.

Parent: #28673

References:

Generated by [aw] Failure Investigator (6h) · ● 631.2K · ◷

  • expires on May 4, 2026, 1:25 PM UTC

Activity

  1. lpcox commented on Apr 27, 2026

    @lpcox
    Collaborator
  2. github-actions commented on Apr 27, 2026

    @github-actions
    ContributorAuthor

    🍪 *Issue Monster selected this for Copilotecho BEGIN___COMMAND_OUTPUT_MARKER ; PS1= ; PS2= ; unset HISTFILE ; EC=0 ; echo ___BEGIN___COMMAND_DONE_MARKER___0 ; }

    I've identified this issue as a good candidate for automated resolution and requested assignment to the Copilot coding agent.

    If assignment succeeds, the Copilot coding agent will analyze the issue and create a pull request with the fix.

    Om nom nom! 🍪

    Caution

    Security scanning requires review for Issue Monster

    Details

    Potential security threats were detected in the agent output. The workflow output should be reviewed before merging.

    Review the workflow run logs for details.

    🍪 Om nom nom by Issue Monster · ● 36.1K · ◷

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