Repository navigation
Description
Workflow Failure
Workflow: Smoke Codex
Branch: main
Run: https://github.com/github/gh-aw/actions/runs/37081140057
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
No Safe Outputs Generated: The agent job succeeded but did not produce any safe outputs.
This typically indicates:
- The safe output server failed to run
- The prompt failed to generate any meaningful result
- The agent should have called
noopto explicitly indicate no action was taken - A
safeoutputsCLI command was malformed and never invoked the CLI
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/github/gh-aw/actions/runs/37081140057
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 smoke-codex failure in https://github.com/github/gh-aw/actions/runs/37081140057
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: falseGenerated from Smoke Codex · codex · 4.9 AIC · ◷
- expires on Oct 3, 2026, 12:19 PM UTC
Activity
github-actions commentedon Oct 3, 2026
Agent job 37091619116 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.
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
No Safe Outputs Generated: The agent job succeeded but did not produce any safe outputs.
Pull Request: #65199
This typically indicates:
noopto explicitly indicate no action was takensafeoutputsCLI command was malformed and never invoked the CLIgithub-actions commentedon Oct 3, 2026
Agent job 37096302208 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.
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
No Safe Outputs Generated: The agent job succeeded but did not produce any safe outputs.
Pull Request: #65199
This typically indicates:
noopto explicitly indicate no action was takensafeoutputsCLI command was malformed and never invoked the CLIgithub-actions commentedon Oct 3, 2026
This issue was automatically closed because it expired on 2026-10-03T12:19:17.648Z.