[aw] Daily Rig Claude Dynamic Workflow Compatibility: has an unavailable configured model
Los mantenedores suelen responder en 1 día
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 2/5
- Tiempo estimado
- 1-3 horas
- Aptitud para principiantes
- 55/100
- Tipo de issue
- Error
- Claridad
- Bastante claro
- Estado de actividad
- Activo
- Stack tecnológico
- github-actions, typescript
- Área
- ci-cd
Línea de trabajo
Start with the workflow source at .github/workflows/daily-rig-claude-compat.md and inspect run 39263565593 to identify the configured model and failure context. Compare its model with the catalog available to the workflow’s Copilot integration; done means the workflow uses a model available in that context and the compatibility run succeeds.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
What happened
Daily Rig Claude Dynamic Workflow Compatibility has an unavailable configured model.
View run #39263565593 · 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/39263565593
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 Oct 26, 2026, 1:57 PM UTC
- Lenguaje dominante
- TypeScript
- Estrellas
- 14
- Forks
- 0
- Merge medio
- 9 h 49 min
- PR fusionados (30 d)
- 32
Preparar el entorno
Este proyecto no incluye contenedor de desarrollo, Dockerfile ni guía de contribución, así que la configuración corre por tu cuenta: empieza por su README y consulta nuestra guía para la primera contribución para los pasos generales.
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de githubnext/rig
-
ai-agent automation
Dificultad 3/5 1-2 días Aptitud para principiantes 52/100
githubnext/rig#683 ·
Los mantenedores suelen responder en 1 día
-
agentic-workflows
Dificultad 4/5 1-2 días Aptitud para principiantes 42/100
githubnext/rig#682 ·
Los mantenedores suelen responder en 1 día
-
ai-agent automation
Dificultad 1/5 Menos de una hora Aptitud para principiantes 1/100
githubnext/rig#681 ·
Los mantenedores suelen responder en 1 día
-
agentic-workflows
Dificultad 5/5 Más de una semana Aptitud para principiantes 20/100
githubnext/rig#679 ·
Los mantenedores suelen responder en 1 día
-
ai-agent automation
Dificultad 3/5 1-2 días Aptitud para principiantes 42/100
githubnext/rig#678 ·
Los mantenedores suelen responder en 1 día
Todos los issues de githubnext/rig
Issues similares
-
Sequências em espanhol: «Atualizado em», a aba «Fila» e o valor 'pause' ainda saem em portuguêsAbierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 77/100
melgarafael/DeskcommCRM#3104 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
Los mantenedores suelen responder en 1 día
-
🐛 [Bug] Mobile: on the login and registration pages the footer sits below the visible screenAbiertobug service: webapp
Dificultad 2/5 1-3 horas Aptitud para principiantes 82/100
Ocelot-Social-Community/Ocelot-Social#10684 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
nicobailon/pi-subagents#2978 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 66/100
getsentry/sentry-conventions#732 · 1 comentario ·
Los mantenedores suelen responder en 1 día