Studio Update: Error Clarity and Automatic Generation Cleanup
Three improvements to the Uwear Studio shipped today. When a generation fails, you now see a specific, actionable error message instead of a generic failure state. Stuck or stale generations clean themselves up automatically. And team accounts now show each member their own results by default, without cross-contamination from teammates.
Generation Failed: Now You Know Why
Until now, a failed generation showed a generic failure indicator. You knew something went wrong, but you had no information about what or what to do next.
The Studio's generation display now reads the specific error message embedded in the generation metadata and surfaces it directly in the UI. If the generation failed because of an unsupported garment type, a resolution issue, or a backend processing problem, you see the actual reason.
What changed
- BeforeFailed generation, no details. Unclear whether to retry, adjust settings, or contact support.
- AfterSpecific error message from generation metadata, displayed in context. Actionable information, right where you need it.
Error messages are shown when the backend populates the metadata error field. If a failure has no error detail attached, the Studio falls back to a standard failure indicator. In practice, most generation errors now carry a message.
No More Ghost Generations
A persistent bug in the Studio caused failed or stuck generations to pile up in the queue indefinitely. Generations in a preparing or error state would linger in the UI even after they were no longer expected to complete, and there was no way to clear them manually.
The Studio now runs an automatic cleanup pass. When generations are detected in preparing or error states that are no longer active, they are removed from the queue without any action required from you. The workspace stays tidy.
How the cleanup works
The cleanup logic runs reactively on state changes in the generation store. It identifies stale entries in preparing or error states, then removes them from the queue. No timers, no manual refresh needed. The queue reflects your actual active and completed generations.
This resolves a long-standing issue reported by Studio users who saw persistent failed-generation notifications they could not dismiss. If you've experienced this, those notifications should now clear automatically on your next session.
Team Accounts: Your Results by Default
For brands using Uwear with multiple team members, generation results are now filtered per user by default. Each team member opens the Studio and sees their own generations, not the full mix of everyone's output.
This is a quality-of-life improvement for teams running concurrent batch generation jobs. Your catalog work stays separate from your colleague's, making it easier to review and act on your own output without filtering through shared results.
All Live in Your Studio
These updates are live in your Uwear Studio account now. No action required on your end. Run a generation, and if something fails, you'll see exactly why.