[aw] Daily Rig Claude Dynamic Workflow Compatibility had a request rejected
維護者通常 1 天內回覆
還沒有人認領這個 Issue。
評估
- 難度
- 3/5
- 預估耗時
- 1-2 天
- 新手友好度
- 45/100
- Issue 類型
- 缺陷
- 描述清晰度
- 基本清楚
- 活躍度
- 活躍
- 技術堆疊
- github-actions, typescript
- 領域
- devtools
研究方向
Start with the linked workflow file, .github/workflows/daily-rig-claude-compat.md, and inspect the failed run to identify which model the workflow requested and whether it is available to the run's Copilot context. The issue suggests checking workflow frontmatter, model availability, and policy settings. Done means the workflow completes successfully with a supported model, or the failure is traced to an external access or policy restriction and documented.
由索引模型根據 Issue 內容生成。
描述
Workflow Failure
Workflow: Daily Rig Claude Dynamic Workflow Compatibility
Branch: main
Run: https://github.com/githubnext/rig/actions/runs/38260069513
[!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.
[!WARNING]
Task Could Not Be Completed: The agent reported that the task could not be performed due to an infrastructure or tool failure.
Error details:
engine_driver_failure
Agent finished without emitting a terminal safe output; task completion could not be confirmed.
Driver exit code: 1. The engine driver exited before a terminal safe output was recorded.
Engine error: Requested model is not supported (model_not_supported_error)
Failure classification: request_rejection
Last engine error type: model_not_supported_error
Retry attempts observed: 0
This is a structured incompletion signal (report_incomplete), not a real task outcome. Any other safe outputs emitted alongside this signal (e.g., comments) describe the failure state, not a completed review or action.
Action Required
Assign this issue to an agent to debug and fix the issue.
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/38260069513
Manually invoke the agent
Debug this workflow failure using your favorite Agent CLI and the agentic-workflows prompt.
- Start your agent
- Load the
agentic-workflowsskill from.github/skills/agentic-workflows/SKILL.mdor https://github.com/github/gh-aw/blob/main/.github/skills/agentic-workflows/SKILL.md - Type
debug the agentic workflow daily-rig-claude-compat failure in https://github.com/githubnext/rig/actions/runs/38260069513
[!TIP]
Stop reporting this workflow as a failure
To stop a workflow from creating failure issues, set
report-failure-as-issue: falsein its frontmatter:safe-outputs: report-failure-as-issue: false
Generated from Daily Rig Claude Dynamic Workflow Compatibility · ◷
- expires on Oct 19, 2026, 2:07 PM UTC
- 主要語言
- TypeScript
- 星號
- 13
- 分支
- 0
- 平均合併
- 3 小時 38 分鐘
- 30 天內合併 PR
- 29
環境準備
這個專案沒有提供開發容器、Dockerfile 或貢獻指南，環境需要你自己搭建：先看它的 README，通用步驟見我們的新手貢獻指南。
從這裡開始
- 先讀完整個 Issue，再讀專案的貢獻指南。
- 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
- Fork 儲存庫，在一個分支上完成修改。
- 送出 Pull Request，並在描述裡引用這個 Issue 編號。
githubnext/rig 的其他 Issue
-
agentic-workflows
難度 3/5 半天 新手友好度 15/100
githubnext/rig#643 ·
維護者通常 1 天內回覆
-
agentic-workflows
難度 4/5 3-5 天 新手友好度 15/100
githubnext/rig#642 ·
維護者通常 1 天內回覆
-
agentic-workflows
難度 3/5 半天 新手友好度 22/100
githubnext/rig#641 ·
維護者通常 1 天內回覆
-
ai-agent automation
難度 4/5 3-5 天 新手友好度 12/100
githubnext/rig#640 ·
維護者通常 1 天內回覆
-
ai-agent automation
難度 3/5 1-3 小時 新手友好度 8/100
githubnext/rig#638 ·
維護者通常 1 天內回覆
相似的 Issue
-
e2e-failure ready-to-code
難度 2/5 1-3 小時 新手友好度 72/100
redhat-developer/rhdh-plugin-export-overlays#4391 · 1 則留言 ·
維護者通常 1 天內回覆
-
難度 1/5 1 小時以內 新手友好度 82/100
Luligu/matterbridge#655 ·
-
難度 2/5 1-3 小時 新手友好度 82/100
software-mansion/argent#1457 ·
維護者通常 1 天內回覆
-
難度 2/5 1-3 小時 新手友好度 62/100
schmayterling/hibi#245 ·
維護者通常 1 天內回覆
-
After a failed save, the red error banner stays on every page until the app is reloaded可能已有人在做 關聯的 PR 仍在進行中或已合併。 未關閉ai-driven-qa bug claude Minor
難度 2/5 1-3 小時 新手友好度 70/100
linagora/twake-contacts-frontend#241 ·
維護者通常 1 天內回覆