Check the saved result before creating another request
A product-video board remains on a spinner, and the creative team is tempted to click Generate again. The visible board is one status surface. Before authorizing another potentially paid operation, check whether the provider already saved the requested result elsewhere.
Kittl's Flows troubleshooting says a board can remain in loading state even though generation finished and was saved in My Creations inside the AI Gallery. This establishes a specific reconciliation path, not a claim that every stuck board has completed. Use the actual job and media evidence rather than assuming either success or failure from one spinner.
Match the result, not merely the thumbnail
| Evidence | Review question | What it does not prove |
|---|---|---|
| Canvas loading state | Which board and request are pending visually? | That no saved result exists |
| Candidate in My Creations | Does it match this source, prompt and request context? | That a similar older thumbnail is the new result |
| Downloaded video | Does the actual file open and contain the intended product? | That product accuracy is approved |
| No matching result | What does the actual provider state establish? | Permission to assume a refund or free retry |
Reconcile a fictional bottle animation
Suppose a merchant requested a bottle clip from artwork R8. My Creations contains a bottle clip from yesterday's R7 and another possible candidate from the current request. Compare the exact source label, brief and available request information. If identity cannot be established, keep the task unresolved; do not select the attractive older clip merely to clear the spinner from the production record.
If a matching result is present, inspect and retain it through the supported workflow before deciding whether another request is necessary. If it is unsuitable, record its real creative defects separately from the canvas status discrepancy. No board or Gallery result was accessed for this fictional exercise.
Keep completion and creative acceptance separate
A finished provider result can still change the cap, logo or label. Review it at normal playback and at important frames against the approved source. Do not call a recovered file “approved” simply because it resolves a pending status.
The pending-generation guide covers wider request-state handling. The dependency guide explains which outputs need rebuilding when inputs change. This named Kittl symptom has an additional saved-result location to inspect before repeating a request.
Close reconciliation when the exact requested output and its actual review state are recorded, or when the unresolved provider condition has an appropriate next owner. CartVisual does not reconcile Kittl jobs, promise refunds or make retries free.