What causes "D-ID Video Stuck Processing (Status Stuck on Started)"?

Queue delays during busy periods or incidents Job failed on the backend without updating the status Webhook not reachable, so you never get the done event Very long scripts or high-resolution inputs

How do I fix "D-ID Video Stuck Processing (Status Stuck on Started)"?

1. Give it time, then refresh: Wait a few minutes and reload the Video Library Check the D-ID status page for an ongoing incident 2. Poll the API correctly: Poll GET /talks/{id} (or /clips/{id}) every few seconds with an overall timeout Treat done, error and rejected as final statuses If you use a webhook, confirm it is publicly reachable and returns 200 3. Resubmit a shorter job: Cancel waiting on the stuck job and create it again Split long scripts into shorter clips 4. Contact support with the job ID: Email support@d-id.com with the talk/clip ID, timestamp and plan Ask for credits back if the stuck job consumed minutes

// troubleshooting guide · d-id

D-ID Video Stuck Processing (Status Stuck on Started)

Status: Ongoing
platforms:: Web, API
updated:: November 15, 2026
reports:: 4
Method: how we research

RUNBOOK · d-id/video-stuck-processing4 FIXES

// quick answer

A D-ID video or API talk that stays on "created" or "started" and never reaches "done" is usually a backend delay or a job that silently failed. Poll with a timeout, treat error/rejected as final, and resubmit or contact support with the ID.

Most likely fix: Give it time, then refresh

How to fix it

// try these in order, the most common fix is first

FIX 1Give it time, then refresh
1. 01Wait a few minutes and reload the Video Library
2. 02Check the D-ID status page for an ongoing incident
Did this fix it?
FIX 2Poll the API correctly
1. 01Poll GET /talks/{id} (or /clips/{id}) every few seconds with an overall timeout
2. 02Treat done, error and rejected as final statuses
3. 03If you use a webhook, confirm it is publicly reachable and returns 200
Did this fix it?
FIX 3Resubmit a shorter job
1. 01Cancel waiting on the stuck job and create it again
2. 02Split long scripts into shorter clips
Did this fix it?
FIX 4Contact support with the job ID
1. 01Email support@d-id.com with the talk/clip ID, timestamp and plan
2. 02Ask for credits back if the stuck job consumed minutes
Did this fix it?

Symptoms

The Studio progress bar sits near the end (often around 99%), or an API talk/clip keeps returning status created or started, or a pending result URL that never becomes downloadable.