[aw] Smoke Copilot BYOK AOAI (api-key): has no AI credits pricing for model (o4-mini-aw)
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 35/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- github, github-actions, typescript
- Domain
- ai-infra-agents, ci-cd, devops
Research direction
Start with the linked workflow source in PR #10307 and inspect its model frontmatter for o4-mini-aw; the linked run reports a missing pricing entry and HTTP 400. Check the AWF pricing configuration or model mapping entry point to determine how workflow models are priced. Done when the workflow model has valid pricing or maps to a priced model and the smoke run can make inference requests.
Written by the indexing model from the issue text.
Description
What happened
Smoke Copilot BYOK AOAI (api-key) has no AI credits pricing for model (o4-mini-aw).
View run #39320945553 · Workflow source · Previous failures
Branch: rabeckett-router-parity-fixtures
Pull Request: #10307
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 has no AI credits pricing: The agent failed because modelo4-mini-awis not in the built-in pricing table and no default fallback pricing is configured. The AWF API proxy rejected every inference request with HTTP 400.
This is a configuration issue — retrying will not help. The model must have pricing before the workflow can run.
How to fix this
Option 1 — Add pricing in the workflow frontmatter:
models:
providers:
github-copilot:
models:
'o4-mini-aw':
cost:
# Placeholder values — replace with actual pricing for this model
input: "0e0" # $0.00 per million input tokens
output: "0e0" # $0.00 per million output tokens
cache_read: "0e0" # $0.00 per million cache-read tokens
cache_write: "0e0" # $0.00 per million cache-write tokens
Use the provider key matching your engine: github-copilot (Copilot), anthropic (Claude), openai (Codex), or google (Gemini). Only input and output are required; the rest default to zero (or output for reasoning).
Option 2 — Map the model to a known model using the models field:
If o4-mini-aw is an alias for a model already in the built-in pricing table, use the models frontmatter field to provide the mapping:
models:
'o4-mini-aw':
- claude-sonnet-4-5
Option 3 — Switch to a model already in the built-in pricing table:
Replace o4-mini-aw in the workflow frontmatter with a model name that the AWF pricing system recognizes (e.g. claude-sonnet-4-5, gpt-4.1, gemini-2.0-flash).
Runtime evidence
[!WARNING]
Task Could Not Be Completed: The workflow recorded areport_incompletesignal: 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 6 tools)
Safe-output CLI calls observed: unknown (not recorded)
Safe-output MCP calls observed: 0
Safe-output persistence: not recorded
Engine error: Model has no AI credits pricing (missing_model_pricing_error)
Agent finished without emitting a terminal safe output; task completion could not be confirmed.
Engine HTTP error codes: 400
Last engine error type: missing_model_pricing_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
No additional engine error was captured. Check the reported failure signals and linked run for details.
Only runtime metadata is shown; agent-generated text is excluded.
Copy a debugging prompt
Paste this into your coding agent:
Debug the agentic workflow "smoke-copilot-byok-aoai-apikey" failure.
Follow https://raw.githubusercontent.com/github/gh-aw/main/debug.md
Failed run: https://github.com/github/gh-aw-firewall/actions/runs/39320945553
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: false
This only disables issue reporting; it does not fix the failure.
Generated from Smoke Copilot BYOK AOAI (api-key) · ◷
- expires on Oct 26, 2026, 8:50 PM UTC
- Dominant language
- TypeScript
- Stars
- 149
- Forks
- 77
- Avg merge
- 4h 19m
- Merged PRs (30d)
- 445
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from github/gh-aw-firewall
-
code-quality refactoring
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
github/gh-aw-firewall#10364 ·
Maintainers usually reply within 1 day
-
code-quality refactoring
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
github/gh-aw-firewall#10363 ·
Maintainers usually reply within 1 day
-
code-quality refactoring
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
github/gh-aw-firewall#10362 ·
Maintainers usually reply within 1 day
-
agentic-workflows automated dependencies
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
github/gh-aw-firewall#3837 ·
Maintainers usually reply within 1 day
-
agentic-workflows
Difficulty 2/5 1-3 hours Newbie friendliness 46/100
github/gh-aw-firewall#10368 ·
Maintainers usually reply within 1 day
All issues in github/gh-aw-firewall
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
diegosouzapw/OmniRoute#17386 ·
Maintainers usually reply within 1 day
-
ready-for-agent
Difficulty 2/5 1-3 hours Newbie friendliness 77/100
Maintainers usually reply within 1 day
-
area/dashboard kind/bug kind/bug-qa QA/dev-automation
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
vybestack/llxprt-code#3917 · 1 comment ·
Maintainers usually reply within 1 day
-
api-parity
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
IBM/carbon-components-ember#1157 ·
Maintainers usually reply within 1 day