Video generation task stuck in queued: how long Seedance tasks normally take and when to worry

A Seedance task in the queued state is waiting for processing and typically moves to succeeded or failed on its own; you monitor it by polling GET /v1/video/generations/{task_id} until the status changes, or by setting metadata.callback_url for webhook delivery. If the request itself errors, no charge applies. According to the official relaydance.com docs, 「Failed or errored requests are never billed」, so a stuck queue never costs you.

What the queued status means and how to check it

The queued status means your task was accepted and is waiting to run, not that it has failed. After you submit a video task with POST /v1/video/generations, you poll GET /v1/video/generations/{task_id} until the status is succeeded or failed, and the succeeded result contains the video url. As an alternative, set metadata.callback_url and the final state is POSTed to your server. Both paths report the same terminal states. Requests use the OpenAI-compatible protocol: 「Set base_url to https://relaydance.com/v1 and keep your OpenAI SDK」, according to the official relaydance.com/docs. Details of each parameter are documented there.

Factors that affect how long a task stays queued

Task duration depends mainly on the requested resolution, clip length, and reference media volume. Clips can run up to 15 seconds, and each request may include up to 9 reference images, 3 reference videos, and 3 audio tracks in metadata.content[], cited in the prompt as @image1 to @imageN. Higher output resolutions carry higher per-second rates: Seedance 2.0 720p is about $0.190 / second, Seedance 2.0 1080p is about $0.470 / second, and native 4K is about $4.90 per 5-second clip. Heavier configurations (longer clips, more references, higher resolution) generally require more processing before the status changes.

Price reference by output setting

Per-second and per-clip rates vary by model and resolution, and live rates are published at relaydance.com/models.

Steps to take when a task appears stuck

When a task stays queued, verify your polling logic and authentication before assuming a fault, since billing is pay-as-you-go and errored requests carry no cost.

1. Confirm your base_url is set to https://relaydance.com/v1.
2. Confirm the header Authorization: Bearer YOUR_API_KEY uses a key created at the console (https://relaydance.com/console).
3. Poll GET /v1/video/generations/{task_id} and read the returned status field.
4. If you configured a webhook, check whether the final state was POSTed to your callback_url.
5. If the request returns an error rather than remaining queued, note that failed or errored requests are never billed.

Frequently asked questions

Will I be charged while a task is queued or if it fails? No. Billing is pay-as-you-go per generated video, and failed or errored requests are never billed.

How do I get the final result? Poll GET /v1/video/generations/{task_id} until status is succeeded (the result contains the video url), or set metadata.callback_url to receive the final state by webhook.

What are the reference media limits per request? Up to 9 reference images, 3 reference videos, and 3 audio tracks, with clips up to 15 seconds.