Skip to content

[aw] Daily Team Evolution Insights failed #37396

@github-actions

Description

@github-actions

Workflow Failure

Workflow: Daily Team Evolution Insights
Branch: main
Run: https://github.com/github/gh-aw/actions/runs/27073188527

⚠️ AI Credits Budget Guidance: The run hit a legacy effective-token rate-limit signal from the API proxy. gh-aw now uses AI Credits (AIC) as the primary cost metric, so migrate per-run budgeting to max-ai-credits.

Why this happened and how to optimize
AIC computation details
# Alias Input Output Cache Read Cache Write ΔAI Credits AI Credits Duration
1 opus48 6,829 20 0 0 3.46 3.46 2.0s
2 opus48 1,632 747 0 45,438 31.1 34.5 7.7s
3 opus48 2 430 45,438 7,739 8.18 42.7 10.7s
4 opus48 2 413 53,177 1,058 4.35 47.1 7.7s
5 opus48 2 756 54,235 3,864 7.02 54.1 10.4s
6 opus48 131 665 58,099 2,788 6.31 60.4 10.6s
7 opus48 2 483 60,887 1,277 5.05 65.5 7.1s
8 opus48 2 204 62,164 594 3.99 69.4 3.6s
9 opus48 2 1,412 62,758 2,194 8.04 77.5 20.3s
10 opus48 2 553 64,952 1,586 5.62 83.1 8.8s
11 opus48 2 4,190 66,538 1,248 14.6 97.7 54.4s
12 opus48 131 237 67,786 4,202 6.61 104.3 4.8s
13 opus48 2 631 71,988 8,778 10.7 115 9.1s
Total 8,741 10,741 668,022 80,766 110.7 2m37s

Legend: Alias shows the model shorthand used in the table. ΔAI Credits is the per-request cost, and AI Credits is the running total computed with the current AI credits pricing model.

Model aliases: opus48=claude-opus-4-8
ET formula: inference_cost_usd ÷ 0.000003 · ET weights: input=1 · cached_input=0.1 · output=4 · reasoning=4 · cache_write=1

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/github/gh-aw/actions/runs/27073188527
Manually invoke the agent

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

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 Daily Team Evolution Insights ·

  • expires on Jun 7, 2026, 8:41 AM UTC

Metadata

Metadata

Type

No type
No fields configured for issues without a type.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions