A picture visible earlier in a chat is not necessarily attached to the next image-editing request. If an edit appears to forget the previous result, inspect the current attachment tray and task record before rewriting the instruction. Wan's image-editing API documents a single-turn input contract. That specific contract does not establish how every chat interface or Imagild carries context.
Check the picture selected for this request
Locate the exact file you want edited and open it outside the conversation. Identify a visible feature that distinguishes it from similar files. Then inspect the image attached beside the current message or in the selected tool's input area. An earlier thumbnail farther up the chat can be conversation history rather than an active attachment. A successful previous upload is not proof of selection in the current task.
For a hypothetical example, the approved poster has a navy border and needs a small scratch removed from an empty corner. The chat still displays that poster, but the composer may contain an older borderless file or no image at all. Check the current thumbnail against the opened approved file. This is an input-presence example, not a reported generation or a recommendation to change the poster's design.
Create a small attachment receipt
Record the task or draft name, selected file and a recognizable visual feature. Where the interface provides a task-details page, inspect its listed inputs too. Do not claim the server received a file merely because it exists on your computer. If the product exposes no received-input record, state that the attachment was checked locally and receipt remains unconfirmed.
| Evidence | Question it answers | Remaining uncertainty |
|---|---|---|
| Opened approved file | Is this the intended source? | Whether it was selected |
| Current input thumbnail | Is the right picture attached now? | Whether the service read it |
| Task's input record, if available | Which source does this task identify? | Whether output preserved it |
| Downloaded result | What actually changed? | Cause requires comparison above |
Ordinary users can complete the first two checks through visible controls. No internal payload inspection is required. API users may optionally retain a non-sensitive file identifier or digest with their documented input items; private signed URLs and credentials do not belong in public notes.
Separate missing source from a bad edit
If the current source is absent or wrong, select the intended file through the supported upload route. Confirm upload processing or any visible availability warning before submitting. For URL-based workflows, confirm that the service is allowed to read the selected source; do not make private material public just to remove an error.
If the correct source is already recorded for the task but its navy border changes in the result, classify that as a preservation failure to investigate. Reattaching the same file repeatedly is not evidence of a fix. Review the permitted change and protected features, preserve the failed result and choose an appropriate supported repair. Correct attachment is necessary input evidence, not a guarantee of accurate generation.
Hand over the current-task evidence
Keep the approved source, current attachment observation, available task record and downloaded output together. Label whether the issue was missing input, wrong input, unreadable input, preservation failure or still unknown. This receipt concerns the current request; a separate version-selection guide decides which earlier result deserves approval. In Imagild, use only the context and attachment behavior actually documented or visible for the selected workflow.
Sources and scope
Prepared by Imagild Editorial with AI assistance. The poster example and receipt are original proposed checks, not an executed API test or a measured model result.