[aw] Deep Report failed
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 68/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- github-actions
- Domain
- ci-cd
Research direction
Inspect .github/workflows/deep-report.md, starting with its workflow frontmatter and configured engine/model, then compare that model with the supported models for the selected provider. Re-run the Deep Report workflow or its failing test path and confirm the invalid-model failure no longer occurs.
Written by the indexing model from the issue text.
Description
Workflow Failure
Workflow: Deep Report
Branch: main
Run: https://github.com/github/gh-aw/actions/runs/36319271490
[!WARNING]
Invalid or Unsupported Model: The agent failed because the configured model name is invalid, unknown, or unavailable for this engine/account.
This is a configuration issue, not a transient error — retrying will not help.
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).
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.
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/36319271490
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 deep-report failure in https://github.com/github/gh-aw/actions/runs/36319271490
[!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 Deep Report · claude · 799.9 AIC · ◷
- expires on Sep 28, 2026, 12:56 AM UTC
- Dominant language
- Go
- Stars
- 5.2k
- Forks
- 547
- Avg merge
- 5h 46m
- Merged PRs (30d)
- 658
Getting set up
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
-
agentic-workflows
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 1 day
-
agentic-workflows
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 1 day
-
agentic-workflows
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 1 day
-
automation code-quality cookie improvement quick-win task-mining
Difficulty 1/5 Under an hour Newbie friendliness 92/100
Maintainers usually reply within 1 day
-
automation code-quality cookie improvement quick-win task-mining
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
Maintainers usually reply within 1 day
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
priority/4/normal status/needs-triage type/bug/unconfirmed
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
authelia/authelia#13292 · 1 comment ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
blinklabs-io/actions#138 ·
Maintainers usually reply within 1 day
-
[UI] AlbumDetails collapses multi-genre list to single primary genre on viewports < lg breakpointOpen
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
bug unconfirmed
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
mudler/LocalAI#12337 · 1 comment ·
Maintainers usually reply within 1 day