Skip to main content
Pay attention to the complete API response when a request fails. The tips below cover common generation failures and the fastest next action for each case.
For the public Seedance video task API, send your portrait image or video as an HTTPS reference URL. GENGEN automatically registers the media in an Asset Group and waits for it to become ready before generation. Poll the returned video task ID while its stage is preparingAssets.To manage reusable assets yourself, create a Virtual Portrait Asset Group, add the media, wait for Result.Status: "Active", and use its asset:// URI in generation requests.Real-Person Verification is intended for situations where another person needs to provide explicit authorization. Create a verification link and send it to that person. After they complete liveness verification, you can upload authorized images, videos, or audio associated with them.See Generate videos with face assets for both methods with step-by-step JSON examples.
On the public Seedance video task API, HTTPS references are registered automatically. If preparation fails, inspect error.message and error.failedAsset on the returned video task.If you manage the asset yourself, poll Get asset until Result.Status is Active, then generate with its asset://<ASSET_ID> URI. Follow the face asset tutorial for the exact requests. Registration does not guarantee that source material or generated output will pass content checks.
Try these steps:
  • Explicitly request fully original background music that does not imitate copyrighted works.
  • Describe the music style, mood, and atmosphere—for example, calm, expressive, and emotionally resonant.
  • Revise the prompt and regenerate. Audio is created anew each time, so retrying the same prompt may also resolve the issue.
For a more reliable workaround:
  • Disable controls.generateAudio if you do not need background music.
  • Provide royalty-free audio that you are permitted to use as an Audio input. This avoids relying on newly generated music and its copyright checks.
Save the complete JSON response, HTTP status, request time, and task ID if one was returned. Send those details to your administrator or support contact, but never include your API key.See Errors for the standard error envelope and retry guidance.
When reporting a failed asynchronous task, include the public GENGEN task ID. It helps identify the task without exposing your API key.