
A confirmed failed Imagild generation releases its reserved points under the current website and API rules. A local timeout or an unknown upstream outcome does not establish confirmed failure. Inspect the saved task's status and usage state before assuming that points should already be available again.
Use the API console for the task contract. There is no release command for clients to call, no promised release deadline in this guide, and no automatic cash-refund conclusion.
Key Takeaways
- Check
data.statustogether withdata.usage.state. - Preserve unresolved tasks rather than creating fresh paid replacements.
- Escalate inconsistent observations with task-level evidence, not account credentials.
Start from the task you actually submitted
Locate the operation record containing the original Idempotency-Key, request parameters and returned task ID. Read GET /tasks/{id} using a valid Bearer key for the owning account.
Active membership is required for this read. A 401 or membership-related 403 prevents observation; it does not establish the task's generation or billing outcome. Fix access before deciding what happened to its reservation.
The status lookup can return HTTP 200 while the task reports failed. The HTTP request retrieved a record successfully; it did not turn failed generation into a successful output.
Choose the next action from the pair of states
| Observation | Appropriate action |
|---|---|
| Failed and released | Record the failure and released reservation |
| Unknown with reserved usage | Preserve identity and seek reconciliation |
| Processing with reserved usage | Continue bounded status checks |
| Succeeded and consumed, but creatively unsuitable | Review the brief; an approved retake is new work |
| Not reserved | Check initialization and submission evidence; do not call it a release |
| Failed but usage appears inconsistent | Keep a sanitized record and request review |
A failed task with released usage does not require another generation to “activate” the release. Repeating a POST is not an account-balance refresh mechanism.
The distinction also protects users who dislike a successful output. Creative rejection should not be relabeled as a provider failure merely to assume another attempt costs nothing.
Compare observations without inventing a timer
Record the time of submission, last successful status read, current task status, points and usage state. If your own page stopped waiting after two minutes, label that as a local wait event.
Do not promise “refunded in two minutes” or start a countdown based on the poll interval. The five-second status hint schedules reads; it is not a reservation-release service-level commitment.
Runware's pricing policy discusses its own treatment of failed generations. That is useful context for why failure and billing deserve explicit documentation, but it is not evidence of an Imagild refund deadline or payment-method refund policy.
Prepare a minimal reconciliation packet
For a private support request, include the Imagild task ID, operation identifier, UTC timestamps, requested model and resolution, last observed status, usage state and safe error code. Include an HTTP request_id only if the relevant error response actually supplied one.
Exclude Bearer keys, raw Authorization headers, account passwords and unrelated private images. A redacted task response is more useful than a screenshot of a large log containing secrets.
The failed-job next-action guide offers a broader diagnostic sequence. The points explanation helps distinguish returned point availability from cash paid for a pack.
Verify your application does not release money locally
Using fixtures, show failed/released, unknown/reserved and succeeded/consumed responses. Confirm that the interface describes each accurately and that none sends an invented refund endpoint.
Refresh a released task twice and check that your own ledger does not count the release twice. For an unknown fixture, verify that no automatic new idempotency key is produced. This local test verifies responsible recovery without paid model calls.
If you later authorize a genuine retake, create a new operation and quote it explicitly. Keep that decision separate from the earlier reservation review so the customer can see what failed, what was released and what new work they approved.
Related tasks
- What Should You Check Before Retrying a Failed Image or Video Job?
- How do Imagild points work for photos and video?
Sources and scope
- Imagild API console: Current active-member access, generation contract and per-task usage fields, independently cross-checked in lib/relay and claims.json dated 2026-10-28.
- Imagild model hub: Current image 10/15/20-point tiers, H3 duration/resolution rates and five-point enhancement option; not a quality or comparative availability benchmark.
- Runware Pricing: General distinction between configuration-based generation pricing, per-request cost and account payment management. Runware-specific fields, features and policies are not attributed to Imagild.
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.