[aw] Daily Rig Claude Dynamic Workflow Compatibility: has an unavailable configured model
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
- 难度
- 2/5
- 预计耗时
- 1-3 小时
- 新手友好度
- 48/100
- Issue 类型
- 缺陷
- 描述清晰度
- 基本清楚
- 活跃度
- 活跃
- 技术栈
- github-actions, typescript
调研方向
Start with .github/workflows/daily-rig-claude-compat.md and inspect the failed run logs for the configured model and request context. Compare the workflow’s model with the catalog available to the agentic-workflows integration; done means selecting an available model or documenting evidence that the failure requires Copilot support.
由索引模型根据 Issue 内容生成。
描述
What happened
Daily Rig Claude Dynamic Workflow Compatibility has an unavailable configured model.
View run #39610622094 · 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/39610622094
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 28, 2026, 1:49 PM UTC
- 主要语言
- TypeScript
- 星标
- 14
- 派生
- 0
- 平均合并
- 9 小时 44 分钟
- 30 天内合并 PR
- 33
环境准备
这个项目没有提供开发容器、Dockerfile 或贡献指南，环境需要你自己搭建：先看它的 README，通用步骤见我们的新手贡献指南。
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
githubnext/rig 的其他 Issue
-
agentic-workflows
难度 4/5 3-5 天 新手友好度 35/100
githubnext/rig#698 ·
维护者通常 1 天内回复
-
agentic-workflows
难度 2/5 1-3 小时 新手友好度 57/100
githubnext/rig#697 ·
维护者通常 1 天内回复
-
ai-agent automation
难度 3/5 1-2 天 新手友好度 52/100
githubnext/rig#696 ·
维护者通常 1 天内回复
-
agentic-workflows
难度 4/5 1-2 天 新手友好度 43/100
githubnext/rig#694 ·
维护者通常 1 天内回复
-
ai-agent automation
难度 5/5 一周以上 新手友好度 1/100
githubnext/rig#693 ·
维护者通常 1 天内回复
相似的 Issue
-
难度 1/5 1 小时以内 新手友好度 68/100
cursor/community-plugins#465 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 66/100
vetro-protocol/vetro-monorepo#978 ·
维护者通常 1 天内回复
-
ai-generated bug category:security effort:s priority:p3
难度 2/5 1-3 小时 新手友好度 67/100
LanternOps/breeze#9697 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 68/100
maniator/verticopolis#1303 · 1 条评论 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 73/100
components-web-app/docs#297 ·