When an image edit ignores a requirement near the end of a long prompt, check whether that text reached the model. Wan’s image-editing API documents a text limit with overflow truncation. A requirement that was cut off is a request-construction problem, distinct from an accepted instruction that the result failed to follow.
Inspect the submitted text, not the writing document
Save the final request after application-added text, translations and reference descriptions have been combined. Compare it with the approved brief. A planning file can contain every requirement while the actual payload contains only its beginning. Confirm the applicable counting rule from the current model documentation; character counts and word counts are different measures.
For a hypothetical edit, a long atmosphere paragraph appears first and “retain the exact package quantity” appears last. If the latter is outside the accepted text range, repeating the request unchanged cannot test whether the model respects the quantity. Do not describe this as deliberate model disobedience when the input evidence is incomplete.
Compress without deleting the contract
Make a checklist of required edits, protected facts and optional mood. Remove repeated adjectives and duplicate camera descriptions before removing obligations. Keep the source identifiers and reference roles unambiguous. If the brief remains too large, simplify the job or plan separate supported stages with explicit approved inputs; splitting text across messages is not automatically equivalent.
| Requirement | Present in approved brief | Present in submitted text | Still inside accepted range |
|---|---|---|---|
| Requested background | Yes | Verify | Verify |
| Face identity | Yes | Verify | Verify |
| Package quantity | Yes | Verify tail | Verify |
| Decorative mood | Optional | Remove repetitions | Lower priority |
This is an editorial audit, not a measured truncation experiment. Fill the last two columns from evidence, and mark receipt unknown when the service does not expose enough information.
Distinguish receipt from compliance
After bringing the request within its documented limit, review the actual output against the obligations. If the quantity is still wrong, record a result failure rather than continuing to blame length. Other explanations include an unreadable source label, conflicting references or the model’s inability to preserve precise lettering. Do not declare a protected requirement solved merely because it now appears earlier in the prompt.
Keep the original approved wording and a short change log showing what was removed. This makes compression reviewable by someone who did not write the revised request. Never silently drop a client requirement to produce an apparently successful sample.
Keep the boundary specific to the service
Use the current model’s published limit and behavior, not a generic rule copied from another provider. Different interfaces may reject overflow instead of truncating it or add their own text. Recheck when the model or integration changes.
In an Imagild project, keep the approved and submitted briefs together where available. This article does not imply that Imagild shares Wan’s truncation behavior or exposes raw request text. Its pass condition is a complete supported request followed by separate inspection of the protected content in the downloaded image.