Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

[aw] Daily Rig Task Generator has model/endpoint mismatch

Abierto
  • ¿Algo no está bien?
#641 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
3/5
Tiempo estimado
Medio día
Aptitud para principiantes
22/100
Tipo de issue
Error
Claridad
Necesita aclaración
Estado de actividad
Activo
Stack tecnológico
github-actions, markdown, yaml
Área
ci-cd

Línea de trabajo

The failing workflow is .github/workflows/daily-rig-task-generator.md; its frontmatter sets the engine, model and timeout-minutes, which the issue says are the places to look. The fix depends on Copilot model policy for the repository, which the issue does not show, so first confirm which model is rejected and whether it is enabled. Done means the workflow run completes without the model-not-supported error and within its timeout.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

agentic-workflows
Workflow Failure

Workflow: Daily Rig Task Generator
Branch: main
Run: https://github.com/githubnext/rig/actions/runs/38407366470

[!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.

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.

Failure Diagnostics

Agent job: agent
Agent job conclusion: cancelled

The model/endpoint mismatch above is the classified cause.

Only runtime metadata is shown; agent-generated text is excluded.

Agent Timed Out: The agent job exceeded the maximum allowed execution time (60 minutes).

To increase the timeout, add or update the timeout-minutes setting in your workflow's frontmatter:

---
timeout-minutes: 70
---
Action Required

Assign this issue to an agent to debug and fix the issue.

Optimize token consumption

This failure was triggered by a guardrail limit (max-turns / timeout). Use this prompt with any coding agent (GitHub Copilot, Claude, Gemini, etc.) to analyze token usage and reduce costs:

Optimize the agentic workflow token consumption using https://raw.githubusercontent.com/github/gh-aw/main/optimize.md

The workflow run is at https://github.com/githubnext/rig/actions/runs/38407366470
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/githubnext/rig/actions/runs/38407366470
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 Rig Task Generator · copilot · 786.9 AIC · ◷

  • expires on Oct 20, 2026, 2:48 PM UTC
Lenguaje dominante
TypeScript
Estrellas
14
Forks
0
Merge medio
3 h 38 min
PR fusionados (30 d)
29

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

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de githubnext/rig

Todos los issues de githubnext/rig

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.