Confirm that the job has actually failed, then inspect the visible error, selected operation, input and point balance before retrying. A general “processing failed” message does not identify the cause by itself. Repeating the same request can consume time or create another chargeable operation without solving the original problem. Make a targeted change only when the evidence supports it.
First identify the operation and state
An uploaded image, a script-generation request, a reference keyframe and a video clip are different operations. Record which one failed and when. Check Jobs or the relevant production panel for the current state. A queued or processing task should not be treated as a confirmed failure merely because the preview has not appeared yet.
If the interface offers task details, open the affected task rather than comparing only the total job count. Keep its identifier for support. Do not assume a new task with a similar thumbnail is the original one; check the operation and creation time so the diagnostic note refers to the right request.
Match the next step to the visible evidence
| Evidence shown | Reasonable next action |
|---|---|
| Unsupported file or size | Check the current upload requirements and replace the input |
| Insufficient points | Reconcile the balance and quoted operation before retrying |
| Content rejection | Review the authorized subject and request; do not assume a server outage |
| Temporary service or network error | Check state and wait or contact support before repeating |
| Generic processing failure | Preserve task details; avoid inventing a precise cause |
This table is a triage aid, not a list of guaranteed Imagild error codes. The interface may show only a general message. In that case, support may need server-side evidence to distinguish provider, download, storage or processing problems. Do not present your guess as a confirmed model failure.
A hypothetical diagnostic note
Example: “Video clip generation failed after submission. The source image uploaded successfully. The task detail shows a general processing error, and the balance needs reconciliation. I have not submitted another copy.” This is an illustrative support note, not a diagnosis of an actual user's task.
The note separates observations from assumptions. It does not say the model rejected the prompt if the screen never showed that. It also explains that a second request was not created, which makes task and billing review simpler.
Review the source without exposing it
Check that the chosen input is the intended reference, readable and authorized. A corrupt file or an inaccessible remote reference can fail before generation; a returned media file can fail later during processing. The same customer-facing message may cover different stages. Avoid posting raw private URLs, credentials or screenshots containing personal information to a public forum.
When using Imagild, share the task identifier and a sanitized description through the appropriate support route. A request for help is not permission to distribute another person's face or the account's API credentials. If additional private media is needed, confirm the destination and purpose first.
Retry as a controlled decision
If the cause is known, correct that cause and submit one intended retry. Check the new quote and balance. Failure refunds depend on the operation and failure path, so do not assume either permanent loss or automatic restoration from the error wording alone. Preserve the original task until the issue is reconciled.
For recurring unexplained failures, stop repeating the operation and report the pattern. Several distinct identifiers and timestamps can be useful; dozens of identical retries rarely make the evidence clearer. A simpler pilot may help only when the issue concerns the generation request, not when the whole service is unavailable.
Does “processing failed” mean the model refused the content?
Not necessarily. It can occur at different stages. Confirm the actual visible or support-provided reason before changing the story or blaming the model.
Should I buy more points immediately?
Only when insufficient balance is the confirmed issue and you intend the new purchase. First reconcile pending operations and any expected refund; adding points does not fix an unrelated service or input failure.