
Let users download successful items from an application batch even when other media tasks fail or remain unresolved. Imagild returns individual tasks, so your batch should preserve per-item task IDs, output access, and usage state. An all-or-nothing “batch failed” screen hides usable results and can encourage unnecessary paid reruns.
Key Takeaways
- Batch status summarizes items; it must not erase each item's actual outcome.
- Successful downloads remain available through authorized delivery when their files are usable.
- Retry or reconcile only the relevant operation, with new creative spend approved explicitly.
Define the batch as an application collection
A batch is your application's set of approved operations, not a new Imagild batch endpoint. Store each item independently with its request, stable key, returned task ID, and observed status.
Use a batch ID for navigation and reporting. Do not send batch_id or an array of requests to the strict single-generation body. A workflow can submit several separately approved items while respecting account write and read limits.
The API console describes individual asynchronous tasks and authenticated output delivery. Active membership remains required for API access, including downloads.
Show a truthful partial-result summary
Consider this illustrative mixed-media batch. Every video is four seconds at 768P with IR disabled:
| Item | Outcome | Quoted points | Observed usage state |
|---|---|---|---|
| Product image | Succeeded | 10 | Consumed |
| Clip A | Succeeded | 60 | Consumed |
| Clip B | Failed | 60 | Released |
| Clip C | Unknown | 60 | Reserved |
The planned generation allocation is 190 points. In this example snapshot, 70 are consumed, 60 released, and 60 still reserved. These are illustrative records, not a live ledger or a guarantee that every unresolved case has identical settlement timing.
The UI can say “Two ready, one failed, one needs review.” It should not say “Nothing generated” or display all 190 points as confirmed final consumption.
Verify current prices in the model market before approving a real workload.
Make successful items independently useful
Each successful card should expose its authorized preview or download action, task reference, and media review state. Your backend must authorize the user and retrieve the owned result with its server-held credential.
An application download path is not the private upstream output_url pasted into a public card. Validate response type and media completeness before offering a saved file.
If you offer “Download ready items,” clearly state which items are included. Build that archive in your own delivery layer, with appropriate streaming and size limits; no Imagild ZIP-export endpoint is implied. Keep failed or unresolved records in the manifest rather than silently omitting them from the batch history.
Give failed and unknown items different actions
A confirmed failed task can show its sanitized error and released usage state. If the user wants another creative attempt after correction, quote and create a new operation linked to that item. Preserve its failed predecessor.
An unknown outcome requires reconciliation. Do not label it a confirmed failure, promise immediate release, or automatically generate a replacement under a new key.
For a missing HTTP acknowledgment, recover the same operation with the saved key and matching parsed parameters. For an existing task ID, read that task. The failed-job guide helps make the distinction visible.
Runware's polling guide shows why asynchronous results require outcome handling. Its batch features or response fields do not define Imagild's individual-task contract.
Test the summary against the item ledger
Use fixtures for the four rows above. Verify that successful downloads work, the failed item does not disable them, and the unknown item remains unresolved after a page refresh. Then simulate a transport error while downloading one successful result; that should not create another generation.
Use points and job planning to communicate the difference between quoted, reserved, consumed, and released work. A partial batch is a recoverable collection of outcomes, not permission to charge for every item again.
Related tasks
- What Should You Check Before Retrying a Failed Image or Video Job?
- Imagild Points, Resolution and Jobs: Plan a Creation Before You Spend
Sources and scope
- Imagild API console: Individual async task records, usage states, private downloads and active membership.
- Imagild model market: Illustrative190-point batch with1K image10 and four-second768P videos60 each.
- Runware Task Polling: Async outcome handling principle only; no Runware batch API or fields transferred.
Product instructions were checked against the current Imagild API contract and the public model catalog. Code, budgets and acceptance checks are illustrative; this article does not claim a new paid generation test, an uptime measurement, a search-volume study or a ranking of AI citations.
Prepared by Imagild Editorial, the company editorial team responsible for these guides. AI assisted research and drafting. This is documentation-based guidance with proposed examples, not a claim of hands-on testing or an independent product review. Report a correction.
Cover: Original Imagild product screenshot captured on 28 October 2026; model availability and prices may change. This image is not an API response or a performance benchmark.