Hacktoberfest 2026: die Issues, die Maintainer für den Oktober markiert haben – offen und einsteigerfreundlich. Hacktoberfest-Issues durchsuchen

[aw] Daily Rig Claude Dynamic Workflow Compatibility had a request rejected

Offen
  • Stimmt etwas nicht?
#646 0 Kommentare 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen

Maintainer antworten meist innerhalb von 1 Tag

Dieses Issue hat noch niemand übernommen.

Bewertung

Schwierigkeit
3/5
Geschätzter Aufwand
Ein halber Tag
Anfängerfreundlichkeit
25/100
Issue-Typ
Bug
Klarheit
Größtenteils klar
Aktivitätsstatus
Aktiv
Tech-Stack
github-actions, markdown
Bereich
ci-cd

Rechercherichtung

Start with the workflow source at daily-rig-claude-compat.md on main and check the model value in its frontmatter, then compare it with the run linked in the issue (actions/runs/38574314987). The fix is a model name the Copilot engine accepts, or a Copilot policy change, and it is done when the workflow run completes without a model_not_supported_error. Access to the repository's Copilot policy settings is likely needed.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

agentic-workflows
Workflow Failure

Workflow: Daily Rig Claude Dynamic Workflow Compatibility
Branch: main
Run: https://github.com/githubnext/rig/actions/runs/38574314987

[!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 workflow recorded a report_incomplete signal: the task was not completed or completion could not be confirmed.

Error details: 
Failure classification: request_rejection
Driver exit code: 1. The engine driver exited before a terminal safe output was recorded.
Last tool call status: not recorded
Failed tool calls observed: 0
Token budget state: unknown (no exhaustion signal recorded)
Step budget state (LLM invocations): unknown (no exhaustion signal recorded)
Safe-output tools: available at gateway snapshot (registered 5 tools)
Safe-output CLI calls observed: unknown (not recorded)
Safe-output MCP calls observed: 0
Safe-output persistence: not recorded
Agent finished without emitting a terminal safe output; task completion could not be confirmed.
Engine error: Requested model is not supported (model_not_supported_error)
Engine HTTP error codes: 400
Last engine error type: model_not_supported_error
Retry attempts observed: 0

A comment or other safe output does not confirm that the requested task was completed. Only inferred runtime status and error codes are reported; agent text is excluded.

Failure Diagnostics

Agent job: agent
Agent job conclusion: failure
Failing step: Execute GitHub Copilot CLI

The runtime did not record a specific cause. Check the linked run for failure details.

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

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/38574314987
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 Claude Dynamic Workflow Compatibility · ◷

  • expires on Oct 21, 2026, 1:49 PM UTC
Vorherrschende Sprache
TypeScript
Sterne
14
Forks
0
Ø Merge
3 Std. 38 Min.
Gemergte PRs (30 T.)
29

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

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus githubnext/rig

Alle Issues in githubnext/rig

Ähnliche Issues

Weitere Issues zu TypeScript

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.