[aw] Daily Rig Claude Dynamic Workflow Compatibility had a request rejected
メンテナーはふだん 1 日以内に返信
まだ誰も着手していません。
評価
- 難易度
- 2/5
- 見積もり時間
- 1〜3時間
- 初心者へのやさしさ
- 28/100
- issue の種類
- バグ
- 明瞭さ
- おおむね明確
- 活発さ
- 活発
- 技術スタック
- github-actions, typescript
- 領域
- devtools
調査の方向性
Start with the workflow at .github/workflows/daily-rig-claude-compat.md and the failed run linked in the issue. Follow the issue’s prompt to consult https://raw.githubusercontent.com/github/gh-aw/main/debug.md and investigate the model_not_supported_error. Done means identifying and fixing the workflow failure; the issue provides no specific code location or expected change.
索引モデルが issue の本文から書いたものです。
説明
Workflow Failure
Workflow: Daily Rig Claude Dynamic Workflow Compatibility
Branch: main
Run: https://github.com/githubnext/rig/actions/runs/38144346303
[!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/38144346303
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/38144346303
[!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 18, 2026, 1:48 PM UTC
- 主要言語
- TypeScript
- スター
- 13
- フォーク
- 0
- 平均マージ
- 1時間 40分
- マージ済み PR（30日）
- 26
環境構築
このプロジェクトには開発コンテナ、Dockerfile、コントリビューションガイドがありません。まず README を読み、一般的な手順ははじめてのコントリビューションガイドを参照してください。
はじめの一歩
- issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
- 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
- リポジトリをフォークし、ブランチを切って変更します。
- issue 番号を参照したプルリクエストを送ります。
githubnext/rig のほかの issue
-
agentic-workflows
難易度 4/5 3〜5日 初心者へのやさしさ 45/100
githubnext/rig#625 ·
メンテナーはふだん 1 日以内に返信
-
ai-agent automation
難易度 1/5 1時間未満 初心者へのやさしさ 15/100
githubnext/rig#624 ·
メンテナーはふだん 1 日以内に返信
-
ai-agent automation
難易度 5/5 1週間以上 初心者へのやさしさ 1/100
githubnext/rig#623 ·
メンテナーはふだん 1 日以内に返信
-
ai-agent automation
難易度 4/5 1〜2日 初心者へのやさしさ 45/100
githubnext/rig#621 ·
メンテナーはふだん 1 日以内に返信
-
ai-agent automation
難易度 2/5 1〜3時間 初心者へのやさしさ 20/100
githubnext/rig#620 ·
メンテナーはふだん 1 日以内に返信
似ている issue
-
./collections should export setUmbracoVersion and setAllowFilePathUploads for in-process consumersオープン
難易度 2/5 1〜3時間 初心者へのやさしさ 78/100
umbraco/Umbraco-CMS-MCP-Dev#563 ·
メンテナーはふだん 1 日以内に返信
-
難易度 2/5 1〜3時間 初心者へのやさしさ 65/100
メンテナーはふだん 1 日以内に返信
-
難易度 2/5 1〜3時間 初心者へのやさしさ 76/100
-
afk-ok area:data-quality importer size:S
難易度 2/5 1〜3時間 初心者へのやさしさ 77/100
enorm-labs/event-junkie#3166 ·
メンテナーはふだん 1 日以内に返信
-
enhancement
難易度 1/5 1時間未満 初心者へのやさしさ 80/100
alunduil/projects-v2-sync#21 ·