Inside QA: Batch Generate Failure Only Shows Generic

When batch generation from silence crashes in ACE-Step, the UI cuts off critical feedback: the bottom GenerationPanel hides failed tracks, and the toast reduces failure to a vague ‘AI generation failed’ - leaving users guessing. This isn’t just a UI flicker; it’s a breakdown in triage. Users can’t see which track failed, let alone why. The root lies in two flaws: first, the toast floods with generic messages, burying per-job errors; second, the panel filters out completed or failed jobs, hiding them from sight. A user once described the experience as ‘trying to fix a broken machine without seeing the fault.’ To fix this, keep failed jobs visible in the bottom panel, render detailed error text there, and enrich the toast with track names and actionable messages. The next time a batch job fails, does the UI let you see the problem, or just a blank?”nnnnnHere is the deal: when a batch fails, the toast must show track-specific errors, not just a generic alert. The bottom panel must keep failed jobs visible until dismissed - no more blind spots. Users deserve clarity, not just a shrug. The bottom line: failure details aren’t optional - they’re essential for trust and control in real-time audio workflows. What’s your biggest pain when a batch job turns silent?”