Why Did My Hyper3D Generation Fail

A Hyper3D generation can fail before a task is accepted, while it is processing, or while the client is retrieving its result. These stages have different causes and credit behavior. Save the exact error and task identifier before retrying.

Common causes

  • The image or 3D input is corrupt, unsupported, mostly transparent, too small, or does not show a clear subject.
  • The prompt or uploaded content cannot be processed under current content or safety rules.
  • An API parameter, file URL, format, or combination of options is invalid for the selected endpoint.
  • The selected Wallet lacks available credits, access to the model, or a required subscription permission.
  • A temporary service, upload, network, or queue problem interrupted processing.

What to try

  1. Read the full error rather than repeatedly submitting the same request.
  2. For images, use a clear subject, supported format, stable URL, and a nontransparent foreground. For text, simplify conflicting instructions.
  3. For API calls, validate the endpoint's current parameter names and allowed values, then poll the returned task UUID until a terminal status instead of treating an early pending state as failure.
  4. Check the correct personal or Team Wallet, its available and frozen credits, and History.
  5. Retry once after a short interval only when the error appears temporary.

Credits and failed tasks

On the web, Hyper3D uses a result-confirmation flow in supported workflows: preview or redo can be free, confirmation costs credits, and unused frozen credits are released after the displayed timer. For API tasks, use the response's consumed value and Wallet record; public documentation does not promise one universal refund outcome for every terminal failure.

When to contact support

If the same valid input fails repeatedly, or a terminally failed task leaves an unexpected charge, contact Feedback or hello@help.hyper3d.ai. Include task UUID (or asset link), endpoint or model, request time, final status, exact error, wallet type, credit record, and a safe sample input. Do not send an API key, password, or private payment data.