Agent job failed but the UI showed success: a status-losing onComplete callback bug
Low_Rush_8535 · reddit · 2026-10-12
The author recounts a bug in their agent-powered content pipeline: a failed job triggered a success toast.
- Root cause wasn't the model: the progress component treated both completed and failed as terminal states, then called onComplete() without passing any status
- The parent treated the callback as success, showed the toast, and immediately unmounted the component — its failure panel never got a chance to render
- Fix: pass status and error through the callback and let the parent choose the notification
- Lesson: regression tests should run a deliberately failed job end-to-end to what the user sees; checking backend error logs wouldn't catch this
More from coding & agent
- Community + AI agents push integer multiplication κ bound up 69% in a day via E8 geometry — CatAstro_Piyush · 2026-10-12
- AI agent deploys a micro factory end-to-end: €20k cost, ROI under 2 years — ihorbeaver · 2026-10-12
- Solo dev uses Claude to build open-source rivals to Adobe and Microsoft Office — mark_k · 2026-10-12
- xtool: open-source Xcode alternative builds and deploys iOS apps on Linux and Windows — sull · 2026-10-12
- Hermes Agent officially ships anatomy skill for wireframes and interactive prototypes — marktenenholtz · 2026-10-12
- One guy cataloged 263 real Grok Bot use cases from 870 replies — thisiskp_ · 2026-10-12