Skip to main content
Use the GENGEN error_code and response HTTP status to handle request failures. The optional error_params.upstreamCode helps identify the corresponding diagnostic code below. Message wording can change; do not use it as a stable identifier. The HTTP headings are reference categories. Always read the actual response status; a successful HTTP 200 task lookup can still report failed generation. Task and partial-image errors may use error.code and error.message instead of the request error envelope. Model service access errors require GENGEN support. You do not need a separate BytePlus account, subscription, or console configuration to call GENGEN.

Diagnose a failed request or task

  1. Check both the HTTP response and the task’s status. A successful task lookup does not mean the video succeeded.
  2. Find the exact diagnostic code in the reference below. Input validation, content rejection, access errors, and temporary capacity limits need different actions.
  3. If you received a task ID, retrieve that task before starting another generation. A timed-out create request may already have been accepted.
For Seedream image edits, HTTP 400 with provider.byteplus_invalid_image_url_invalid_format means Seedream could not read a reference image. The diagnostic may say Invalid base64 image_url even when you supplied a URL. Fetch each URL in assets.referenceImages without login and check that the final response contains a valid image. A temporary URL may expire or redirect to an HTML page. Keep the image accessible until generation finishes. Errors such as InputImageSensitiveContentDetected and OutputVideoSensitiveContentDetected identify whether the rejection concerns an input or a generated output. Review the specific prompt or media involved before trying again; repeating the same request is not a reliable fix.
  • OutputVideoSensitiveContentDetected.PolicyViolation can indicate copyright restrictions in the generated video. Review the supplied material and prompt, or ask support to investigate the task.
  • InputImageSensitiveContentDetected.PrivacyInformation can indicate a real-person image restriction. Check the selected workflow’s input requirements and use an appropriate image.
  • An HTTP 403 is not always a content rejection. Find its diagnostic code below to distinguish permissions, service access, and resource-state errors.
Changing models is a separate request with its own capabilities, input requirements, pricing, and content policies. GENGEN does not automatically switch a rejected Seedance task to Wan Spicy or Kling.

Continue with GENGEN

For an existing failed request, contact support with the diagnostics listed below. If you are integrating Seedance for the first time, follow the API quickstart, review Seedance 2.5 capabilities, and check current prices before creating a task.

HTTP 400

HTTP 401

HTTP 403

HTTP 404

HTTP 405

HTTP 429

HTTP 500

HTTP 502

HTTP 503

HTTP 504

Support diagnostics

Include the HTTP status, GENGEN error_code, diagnostic code, request time, model, and public task ID when available. Never include your API key. See Error handling for the response envelope and safe retry guidance.