Manage Generated Image Jobs and Failures
Design a job history that helps a creative team find prior image runs, understand partial failures, and retry without losing settings or successful results.
The brief
Understand the problem
Background
Image generation work often spans several variants, references, aspect ratios, and processing stages. When one result fails, a generic error can make people rerun the full batch, spend more credits, or lose track of which settings produced an approved image.
User context
Ren creates six campaign illustrations from one brief. Four finish, one is blocked by a reference-file error, and one times out during upscaling after the team has already commented on the successful results.
Product problem
Creators need a durable record of inputs, outputs, cost, and failure stage, plus recovery actions that do not duplicate completed work or detach team feedback.
Objective
Create job-history search, run detail, partial-failure recovery, and result comparison for one creative project.
What to design
Define the experience
Required experience
- Find a prior job by project, date, status, or settings
- Inspect the exact inputs, versions, results, and processing stages
- Retry only a failed variant with a clear cost preview
- Compare recovered output with successful results and preserve comments
Screens and states
- Job history
- Run detail
- Failure recovery
- Result comparison
Core user flow
Follow the critical path
- 01
Ren filters the campaign project to jobs with partial failure
- 02
He opens the six-variant run and sees four complete, one reference error, and one upscale timeout
- 03
He replaces the unreadable reference for one variant and retries the upscale for the other
- 04
The service previews two additional credits before submission
- 05
Recovered results join the original run with input lineage and existing comments intact
Product rules
Requirements and constraints
Requirements
- Store prompt, parameters, references, model version, creator, time, and project for each run
- Show status and cost at both run and individual-result level
- Explain whether failure occurred before generation, during rendering, or during post-processing
- Offer retry, duplicate with edits, archive, and delete as distinct actions
- Keep new results linked to the exact input version and originating failure
Constraints
- Deleted source references may not be recoverable
- Retrying can produce a different visual result even with the same settings
- Usage cost must be confirmed before any billable retry
Reality check
States worth considering
Finish line
What to deliver
- Four desktop screens showing searchable history, mixed job states, selective retry, and lineage-aware comparison
If you want more
Optional extensions
Optional direction
Visual resources
Use these as a starting constraint if you want one. They are not part of the required solution.