[aw] Daily Rig Claude Dynamic Workflow Compatibility: has an unavailable configured model
Maintainer antworten meist innerhalb von 1 Tag
Dieses Issue hat noch niemand übernommen.
Bewertung
- Schwierigkeit
- 2/5
- Geschätzter Aufwand
- 1-3 Stunden
- Anfängerfreundlichkeit
- 25/100
- Issue-Typ
- Bug
- Klarheit
- Größtenteils klar
- Aktivitätsstatus
- Aktiv
- Tech-Stack
- github-actions, typescript
- Bereich
- ci-cd
Rechercherichtung
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.
Vom Indexierungsmodell aus dem Issue-Text verfasst.
Beschreibung
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
- Vorherrschende Sprache
- TypeScript
- Sterne
- 14
- Forks
- 0
- Ø Merge
- 9 Std. 27 Min.
- Gemergte PRs (30 T.)
- 34
Entwicklungsumgebung
Dieses Projekt bietet weder Dev-Container noch Dockerfile noch Beitragsleitfaden – die Einrichtung liegt bei Ihnen. Beginnen Sie mit der README; die allgemeinen Schritte stehen in unserem Leitfaden für den ersten Beitrag.
Erste Schritte
- Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
- Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
- Forken Sie das Repository und arbeiten Sie in einem Branch.
- Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.
Mehr aus githubnext/rig
-
agentic-workflows
Schwierigkeit 5/5 Über eine Woche Anfängerfreundlichkeit 25/100
githubnext/rig#745 ·
Maintainer antworten meist innerhalb von 1 Tag
-
ai-agent automation
Schwierigkeit 4/5 3-5 Tage Anfängerfreundlichkeit 20/100
githubnext/rig#743 ·
Maintainer antworten meist innerhalb von 1 Tag
-
agentic-workflows
Schwierigkeit 4/5 1-2 Tage Anfängerfreundlichkeit 43/100
githubnext/rig#742 ·
Maintainer antworten meist innerhalb von 1 Tag
-
ai-agent automation
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 48/100
githubnext/rig#740 ·
Maintainer antworten meist innerhalb von 1 Tag
-
agentic-workflows
Schwierigkeit 4/5 3-5 Tage Anfängerfreundlichkeit 35/100
githubnext/rig#739 ·
Maintainer antworten meist innerhalb von 1 Tag
Ähnliche Issues
-
Schwierigkeit 1/5 1-3 Stunden Anfängerfreundlichkeit 66/100
Maintainer antworten meist innerhalb von 1 Tag
-
area:plugins area:security area:skills bug has repro
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 76/100
anthropics/claude-code#105911 ·
Maintainer antworten meist innerhalb von 1 Tag
-
documentation good first issue help wanted
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 74/100
dev-five-git/devup-ui#879 ·
Maintainer antworten meist innerhalb von 11 Tagen
-
openspec-apply-change skill: when blocked, may select a ready artifact unrelated to missingArtifactsOffen
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 72/100
Fission-AI/OpenSpec#2165 ·
Maintainer antworten meist innerhalb von 1 Tag
-
🐞 bug 🧐 unconfirmed
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 66/100
Tencent/tdesign-vue-next#7032 · 1 Kommentar ·
Maintainer antworten meist innerhalb von 1 Tag