[aw] Daily Rig Claude Dynamic Workflow Compatibility: has an unavailable configured model
I maintainer di solito rispondono entro 1 giorno
Nessuno ha ancora preso questa issue.
Valutazione
- Difficoltà
- 2/5
- Tempo stimato
- 1-3 ore
- Idoneità per principianti
- 25/100
- Tipo di issue
- Bug
- Chiarezza
- Abbastanza chiara
- Stato di attività
- Attiva
- Stack tecnologico
- github-actions, typescript
- Ambito
- ci-cd
Direzione di ricerca
Start with the failing run and the workflow source at .github/workflows/daily-rig-claude-compat.md; inspect its frontmatter model and compare it with the model catalog available to the Copilot workflow integration. Done when the workflow uses a model available in that context and a subsequent compatibility run succeeds. The payload does not identify a specific test or code file.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Descrizione
What happened
Daily Rig Claude Dynamic Workflow Compatibility has an unavailable configured model.
View run #40698470349 · Workflow source · Previous failures
Branch: main
Next step
Review the failure details below for a targeted fix, or assign this issue to a coding agent to investigate.
Failure details
[!WARNING]
Model Not Supported: The requested model was rejected by the provider for this request.
This may be an invalid model name, a policy or access restriction for this token/repository, or a change in provider availability. Retrying the same session will not resolve a model that remains unavailable.
Copilot also filters models by integration. A model enabled by organization policy and available in the standalone CLI can still be unavailable to the agentic-workflows integration. In particular, Gemini models have been absent from that integration's catalog. The bundled gh-aw model catalog is not proof of live access. Select a model offered to this workflow; enabling a missing model for agentic-workflows requires Copilot API support. Do not change the integration ID to bypass access policy.
How to fix this
Specify a valid model for the selected engine in the workflow frontmatter:
---
engine: copilot
model: gpt-5-mini
---
To find valid models, check your engine/provider documentation (for Copilot see supported models) and the model catalog returned for the failing token/context.
If the model previously worked with the same workflow and token type, compare the successful and failing runs' model catalogs and request context. If the catalog changed, share sanitized timestamps, repository/organization context, and Copilot service request IDs with the Copilot model-access support team. Do not share tokens.
If the error text is No model available. Check policy enablement under GitHub Settings > Copilot, the model is not disabled in the workflow but by Copilot policy. Enable the model under GitHub Settings > Copilot > Policies for the org/repo, or pick a model that is already enabled. This can also be triggered by a subagent (task tool) dispatch requesting a model that the policy does not allow, even when the main agent's model is enabled.
[!WARNING]
Engine Failure: Thecopilotengine terminated unexpectedly.
Error details:
Driver exit code: 1
Review the workflow run logs for diagnostics. Raw agent output is omitted because it may contain secrets.
Copy a debugging prompt
Paste this into your coding agent:
Debug the agentic workflow "daily-rig-claude-compat" failure.
Follow https://raw.githubusercontent.com/github/gh-aw/main/debug.md
Failed run: https://github.com/githubnext/rig/actions/runs/40698470349
If the repository includes the agentic-workflows skill, load it before investigating.
Manage failure notifications
To stop creating failure issues for this workflow, set this in its frontmatter and recompile:
safe-outputs:
report-failure-as-issue: false
This only disables issue reporting; it does not fix the failure.
Generated from Daily Rig Claude Dynamic Workflow Compatibility · ◷
- expires on Nov 4, 2026, 1:44 PM UTC
- Lingua principale
- TypeScript
- Stelle
- 14
- Fork
- 0
- Merge medio
- 9h 27m
- PR unite (30g)
- 34
Preparare l'ambiente
Questo progetto non fornisce container di sviluppo, Dockerfile né guida per i contributori, quindi l'ambiente è a tuo carico: parti dal suo README e consulta la nostra guida al primo contributo per i passaggi generali.
Come iniziare
- Leggi tutta la issue e poi la guida ai contributi del progetto.
- Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
- Fai un fork del repository e lavora su un branch.
- Apri una pull request che faccia riferimento al numero della issue.
Altre issue di githubnext/rig
-
agentic-workflows
Difficoltà 5/5 Più di una settimana Idoneità per principianti 25/100
githubnext/rig#745 ·
I maintainer di solito rispondono entro 1 giorno
-
ai-agent automation
Difficoltà 4/5 3-5 giorni Idoneità per principianti 20/100
githubnext/rig#743 ·
I maintainer di solito rispondono entro 1 giorno
-
agentic-workflows
Difficoltà 4/5 1-2 giorni Idoneità per principianti 43/100
githubnext/rig#742 ·
I maintainer di solito rispondono entro 1 giorno
-
ai-agent automation
Difficoltà 2/5 1-3 ore Idoneità per principianti 48/100
githubnext/rig#740 ·
I maintainer di solito rispondono entro 1 giorno
-
agentic-workflows
Difficoltà 4/5 3-5 giorni Idoneità per principianti 35/100
githubnext/rig#739 ·
I maintainer di solito rispondono entro 1 giorno
Tutte le issue di githubnext/rig
Issue simili
-
fix(worker): keep normal prepare waiting states failure-freeForse già presa @LichKing-2234 l’ha presa oggi. Apertaagent:codex priority:P1
Difficoltà 2/5 1-3 ore Idoneità per principianti 72/100
AgoraIO-Extensions/agent-infra#3745 ·
I maintainer di solito rispondono entro 1 giorno
-
The five-line work window can drop its oldest line: the per-line byte share ignores the JSON framingForse già presa @Eapp1e l’ha presa oggi. Aperta
Difficoltà 2/5 1-3 ore Idoneità per principianti 84/100
makecindy/cindy#7973 · 1 commento ·
I maintainer di solito rispondono entro 1 giorno
-
community first-timers-only good first issue hacktoberfest help wanted low hanging fruit up-for-grabs
Difficoltà 1/5 Meno di un'ora Idoneità per principianti 78/100
lingdojo/kana-dojo#33337 · 1 commento · 5 reazioni ·
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 76/100
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 78/100
code-yeongyu/senpi#4917 · 1 commento ·
I maintainer di solito rispondono entro 1 giorno