Repository navigation
[aw] Smoke Copilot Sub Agents: has an unavailable configured model #70631
Description
What happened
Smoke Copilot Sub Agents has an unavailable configured model.
View run #39499460077 · Workflow source · Previous failures
Branch: copilot/fix-copilot-sub-agent-models
Pull Request: #70389
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: The copilot engine 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 "smoke-copilot-sub-agents" failure.
Follow https://raw.githubusercontent.com/github/gh-aw/main/debug.md
Failed run: https://github.com/github/gh-aw/actions/runs/39499460077
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: falseThis only disables issue reporting; it does not fix the failure.
Generated from Smoke Copilot Sub Agents · ◷
- expires on Oct 21, 2026, 9:25 AM UTC
Activity
github-actions commentedon Oct 20, 2026
Agent job 39508150750 failed.
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-workflowsintegration. 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 foragentic-workflowsrequires 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:
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 (tasktool) dispatch requesting a model that the policy does not allow, even when the main agent's model is enabled.Warning
Engine Failure: The
copilotengine terminated unexpectedly.Error details:
Review the workflow run logs for diagnostics. Raw agent output is omitted because it may contain secrets.
github-actions commentedon Oct 21, 2026
Agent job 39519710217 failed.
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-workflowsintegration. 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 foragentic-workflowsrequires 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:
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 (tasktool) dispatch requesting a model that the policy does not allow, even when the main agent's model is enabled.Warning
Engine Failure: The
copilotengine terminated unexpectedly.Error details:
Review the workflow run logs for diagnostics. Raw agent output is omitted because it may contain secrets.
pelikhan commentedon Oct 21, 2026
Resolved in code by merged PR #70652, which replaces the unavailable workflow-declared sub-agent model pins and preserves fail-closed resolution. The original and subsequently linked failure runs predate that merge (2026-10-21 00:46:27 UTC). Closing this historical model-pin incident; this is not a claim of post-merge hosted verification or resolution of unrelated smoke failures.