[aw] Daily Rig Claude Dynamic Workflow Compatibility: has an unavailable configured model
Mantenedores costumam responder em até 1 dia
Ninguém assumiu esta issue ainda.
Avaliação
- Dificuldade
- 2/5
- Tempo estimado
- 1-3 horas
- Facilidade para iniciantes
- 38/100
- Tipo de issue
- Bug
- Clareza
- Razoavelmente clara
- Status de atividade
- Ativa
- Stack de tecnologia
- github-actions, typescript
- Domínio
- ci-cd
Direção de pesquisa
Read the workflow source at .github/workflows/daily-rig-claude-compat.md and inspect run #40198818915 for the model sent to Copilot and its failure details. Compare that model with the catalog available to the workflow token; done means the workflow selects an available model and a run completes successfully.
Escrita pelo modelo de indexação a partir do texto da issue.
Descrição
What happened
Daily Rig Claude Dynamic Workflow Compatibility has an unavailable configured model.
View run #40198818915 · 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/40198818915
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 1, 2026, 1:46 PM UTC
- Linguagem predominante
- TypeScript
- Estrelas
- 14
- Forks
- 0
- Merge médio
- 9h 27min
- PRs com merge (30d)
- 34
Preparar o ambiente
Este projeto não oferece contêiner de desenvolvimento, Dockerfile nem guia de contribuição, então a configuração fica por sua conta: comece pelo README e veja nosso guia da primeira contribuição para os passos gerais.
Primeiros passos
- Leia a issue inteira e depois o guia de contribuição do projeto.
- Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
- Faça um fork do repositório e trabalhe em uma branch.
- Abra um pull request que referencie o número da issue.
Mais de githubnext/rig
-
agentic-workflows
Dificuldade 5/5 Mais de uma semana Facilidade para iniciantes 25/100
githubnext/rig#724 ·
Mantenedores costumam responder em até 1 dia
-
ai-agent automation
Dificuldade 1/5 Menos de uma hora Facilidade para iniciantes 1/100
githubnext/rig#723 ·
Mantenedores costumam responder em até 1 dia
-
agentic-workflows
Dificuldade 4/5 3-5 dias Facilidade para iniciantes 35/100
githubnext/rig#722 ·
Mantenedores costumam responder em até 1 dia
-
ai-agent automation
Dificuldade 1/5 Menos de uma hora Facilidade para iniciantes 10/100
githubnext/rig#721 ·
Mantenedores costumam responder em até 1 dia
-
agentic-workflows
Dificuldade 4/5 3-5 dias Facilidade para iniciantes 35/100
githubnext/rig#719 ·
Mantenedores costumam responder em até 1 dia
Todas as issues de githubnext/rig
Issues semelhantes
-
DRY stats column groupingsAbertaready
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 63/100
wheresrhys/totf#1214 ·
Mantenedores costumam responder em até 1 dia
-
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 78/100
CodeChefVIT/ffcs#281 ·
Mantenedores costumam responder em até 2 dias
-
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 82/100
Mantenedores costumam responder em até 1 dia
-
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 83/100
endora-commerce/endora-commerce#451 ·
Mantenedores costumam responder em até 1 dia
-
enhancement
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 65/100
vetro-protocol/vetro-monorepo#1007 ·
Mantenedores costumam responder em até 1 dia