[aw] CI Optimization Coach failed

[aspire-repo-bot]

Workflow Failure

Workflow: CI Optimization Coach
Branch: main
Run: https://github.com/microsoft/aspire.dev/actions/runs/26764432125

⚠️ Engine Failure: The copilot engine terminated unexpectedly.

Last agent output:

Authentication failed with provider at http://172.30.0.30:10002 (HTTP 401).
  Check your COPILOT_PROVIDER_API_KEY or COPILOT_PROVIDER_BEARER_TOKEN.
Changes   +0 -0
Duration  0s

Action Required

Assign this issue to an agent to debug and fix the issue.

Debug with any coding agent

Use this prompt with any coding agent (GitHub Copilot, Claude, Gemini, etc.):

Debug the agentic workflow failure using https://raw.githubusercontent.com/github/gh-aw/main/debug.md

The failed workflow run is at https://github.com/microsoft/aspire.dev/actions/runs/26764432125

Manually invoke the agent

Debug this workflow failure using your favorite Agent CLI and the agentic-workflows prompt.

• Start your agent
• Load the agentic-workflows prompt from .github/agents/agentic-workflows.agent.md or https://github.com/github/gh-aw/blob/main/.github/agents/agentic-workflows.agent.md
• Type debug the agentic workflow ci-coach failure in https://github.com/microsoft/aspire.dev/actions/runs/26764432125

Tip

Stop reporting this workflow as a failure

To stop a workflow from creating failure issues, set report-failure-as-issue: false in its frontmatter:

safe-outputs:
  report-failure-as-issue: false

Generated from CI Optimization Coach · ◷

• expires on Jun 8, 2026, 3:30 PM UTC

[IEvangelist]

Triage note — recurring duplicates

This is the 2nd open occurrence of [aw] CI Optimization Coach failed from the same workflow (ci-coach). Both are the same copilot engine HTTP 401 against the provider at 172.30.0.30:10002, just different runs.

Older duplicate (recommend closing in favor of this latest one):

• [aw] CI Optimization Coach failed #1065

Recommendation:

• Close [aw] CI Optimization Coach failed #1065 as duplicate of this issue.
• Underlying provider auth needs investigation (COPILOT_PROVIDER_API_KEY / COPILOT_PROVIDER_BEARER_TOKEN) — same root cause as the Integration Data Updater family tracked on [aw] Integration Data Updater failed #1151.
• Consider configuring ci-coach to update an existing open failure issue (or skip filing) instead of opening a new one per failed run.

Not closing anything here — leaving that to a maintainer.