Multiple issue with Sora 2 API

[user9]

1. Forever in-progress

Video stucks at a random progress (E.g. 10%) forever.

Credited is deducted.

2. Fail after 100% progress

• T + 1min = 53% in progress
• T + 2min = 89% in progress
• T + 3min = 100% in progress
• T + 4min = failed

Credited is deducted.

{"video_status" =>
  {"id" => "video_68e669d2...551e79afad",
   "object" => "video",
   "created_at" => 1759930835,
   "status" => "failed",
   "completed_at" => nil,
   "error" => nil,
   "expires_at" => nil,
   "model" => "sora-2",
   "progress" => 100,
   "remixed_from_video_id" => nil,
   "seconds" => "12",
   "size" => "1280x720"}
}

Anyone got a solution or walk-around?

[_j]

I think the solution might be “wait and see”. See if others are willing to continue against a service that is taking credits and not delivering a product. More anecdote:

Sora 2 API - Video Generation Stuck in in_progress State

Yes , hit the same issue yesterday on agent. Several pipeline runs got stuck at progress 100% for individual scenes. See this task ID for example - video_68e5b1cb755081918b0c51027a44494a050546e42aa64899 Stuck at progress 100% since last hour. { “id”: “video_68e5b1cb755081918b0c51027a44494a050546e42aa64899”, “object”: “video”, “created_at”: 1759883723, “status”: “in_progress”, “completed_at”: null, “error”: null, “expires_at”: null, “model”: “sora-2-pro”, “progress”: 100, “remixed_fr…

Sora 2 API charges money on failed run at 100% progress

Hello, Was wondering if anyone runs into the same issue with the new Sora 2 API in which the request failed at 100 progress, yet still charges money? Here’s the details from the video.list() { "id": "video_68e482d165c481918c06309f2791a1b00f353fccf1b961dc", "object": "video", "created_at": 1759806161, "status": "failed", "completed_at": null, "error": null, "expires_at": null, "model": "sora-2", "progress": 100, "remixed_from_vide…

The status channel of the API doesn’t have a ‘refused’ or ‘safety’ to know if it was erroneous vision inspection or whatnot that failed out the API call.

status:
type: string
enum:
  - queued
  - in_progress
  - completed
  - failed

And a null “error” field that doesn’t provide the “why generation failed” of a described object doesn’t build confidence.

error:
anyOf:
    properties:
      code:
        type: string
      message:
        type: string
    type: object
    required:
      - code
      - message
    description: Error payload that explains why generation failed, if applicable.
  - type: 'null'