[aw] Issue Triage (skills-driven) could not verify daily AI credits

Aperta
#14,842 2 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
35/100
Tipo di issue
Bug
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
github-actions, go
Ambito
ci-cd, devops

Direzione di ricerca

Start with the linked workflow run and the Issue Triage workflow at .github/workflows/issue-triage.md; the issue says the guardrail returned transient_error because it could not verify daily AI Credits, with “Server Error” as the reason. Follow the workflow’s credit accounting and GitHub API checks to identify why verification failed. Done means the underlying cause is fixed and the guardrail can reliably verify prior runs.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

agentic-workflows needs-triage
Workflow Failure

Workflow: Issue Triage (skills-driven)
Branch: trunk
Run: https://github.com/cli/cli/actions/runs/40531178490

[!WARNING]
Daily Workflow AI Credits Could Not Be Verified: The agent was not started because the daily guardrail could not prove complete AI Credits accounting for earlier workflow runs.

Guardrail status: transient_error

Reason: Daily workflow AI Credits are unknown: Server Error

The guardrail fails closed either because a billable component's usage artifact is missing, empty, or unreadable, or because the guardrail could not reach the GitHub API to verify prior runs. The detailed reason above identifies the specific cause.

This is typically a transient GitHub API failure, such as a network error or rate limiting. The guardrail will retry automatically on the next run; no action is required unless the failures persist.

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/cli/cli/actions/runs/40531178490
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 Issue Triage (skills-driven) · ◷

  • expires on Nov 3, 2026, 3:29 PM UTC
Lingua principale
Go
Stelle
46.8k
Fork
9.2k
Merge medio
1g 14h
PR unite (30g)
60

Preparare l'ambiente

Apri in Codespaces

Avvia il container di sviluppo del progetto nel browser, con il tuo account GitHub.

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di cli/cli

Tutte le issue di cli/cli

Issue simili

Altre issue su Go

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.