Give every AI-generated product image render an immutable attempt key, and publish a tenant-scoped pointer only after the render record is durably committed. A retry must create another candidate, never compete for the same object name. That decision preserves a recovery path when an image appears missing even though a storage request succeeded.
Short answer: diagnose the job and its publication record before inspecting the image URL; if a retry reused the same key, no-version storage cannot recover the bytes that the later write replaced.
This is an access-control problem disguised as a filename problem. In a media catalog, the image is addressed by a tenant, product, and render job, while the worker sees a convenient path such as products/42/latest.png . A caller can time out after the upload has completed, retry, and produce a second valid image. Both workers then have a plausible claim on one name.…