"No solution found" provides no context about why Seer couldn't produce a plan.
What happens
When sentry issue plan completes but Seer produces no solution artifact, formatPlanOutput() in src/commands/issue/plan.ts outputs:
No solution found. Check the Sentry web UI for details.
This gives the user no indication of why no solution was produced. The Sentry web UI may not have more detail either.
Observed case
- Issue DOCS-84Y — "HTTP/1.1 Overhead"
- Root cause: network intermediary downgrades HTTP/2 → HTTP/1.1 (infrastructure-level, not a code bug)
- Seer examined
src/mdx.ts and app/layout.tsx but couldn't map the root cause to a code fix
- Autofix API returned
status: COMPLETED with solution: null on cause 0
Suggested improvement
- Surface Seer's reason when available (e.g., "root cause is infrastructure-level, no code fix identified")
- At minimum, show what files were examined and that no actionable code change was found
- Consider distinguishing "Seer tried and couldn't fix this" from "Seer errored out"
References
src/commands/issue/plan.ts — formatPlanOutput()
- Autofix API state for the issue confirms
solution: null with status: COMPLETED
Action taken on behalf of Burak Yigit Kaya.
"No solution found" provides no context about why Seer couldn't produce a plan.
What happens
When
sentry issue plancompletes but Seer produces no solution artifact,formatPlanOutput()insrc/commands/issue/plan.tsoutputs:This gives the user no indication of why no solution was produced. The Sentry web UI may not have more detail either.
Observed case
src/mdx.tsandapp/layout.tsxbut couldn't map the root cause to a code fixstatus: COMPLETEDwithsolution: nullon cause 0Suggested improvement
References
src/commands/issue/plan.ts—formatPlanOutput()solution: nullwithstatus: COMPLETEDAction taken on behalf of Burak Yigit Kaya.