Sora 2 Deducts Credits on Failed Generations (2026)
Sora 2 via Adobe Firefly deducts credits on 'service unavailable' errors with nothing generated — documented on Adobe's forum, unresolved 6 months later.
This isn't a rumor pulled from a review aggregator — it's a bug report sitting on Adobe's own public community forum, filed against Sora 2 as accessed through Adobe Firefly's partner-model integration. The claim is simple and verifiable: the generation fails with a server error, no video is produced, and the credits are deducted anyway. Six months after it was first reported, another user confirmed the identical bug is still happening.
Update: the Sora API is sunsetting September 24, 2026
OpenAI discontinued the consumer Sora app back in April 2026, and the Sora API — the access path Adobe Firefly uses for this integration — is scheduled to shut down entirely on September 24, 2026. Everything documented below is real and was still reproducing at the time of writing, but the integration itself has a hard expiration date, so anyone relying on Sora 2 through Firefly needs a fallback before then.
We're citing this one directly because we could verify it firsthand — a rare case where the exact source, the exact quotes, and the exact dates are all a click away.
The Documented Bug Report
On Adobe's community forum, a thread titled “I am losing credits when generative AI requests fail” lays out the issue plainly. The original poster, user MatheusdeFranco, reported on February 5, 2026:
“I am losing credits when generative AI requests fail. Sora 2 returned a service unavailable error twice, no content was generated, yet credits were deducted.”
That would be a one-off complaint if it stopped there. It didn't. On August 11, 2026 — over six months later — a second user, Michael_I, replied to the same thread:
“I have exactly the same problem today.”
You can read the full thread yourself at Adobe's community bug-reports board . It's filed under Adobe's own bug-tracking category, meaning Adobe's support structure has acknowledged it as a reportable issue rather than a one-time fluke — and it was still reproducing, unresolved, half a year after the first report.
Why This Is Worse Than a Standalone Sora Bug
This specific case runs through Adobe Firefly's partner-model integration — the layer Adobe built so Creative Cloud subscribers can access Sora 2 without leaving Adobe's ecosystem (a pathway that itself has a shelf life — OpenAI is sunsetting the Sora API on September 24, 2026). That framing matters: users reaching for Sora 2 via Firefly are often professional creatives paying for what's positioned as an enterprise-grade, reliable pipeline. Finding the exact same “error out, lose your credits anyway” failure mode that's common across consumer AI video tools — inside a paid professional suite — is a worse surprise than expecting it from a free-tier generator.
And the six-month gap between the first report and the confirmed repeat says something on its own: this isn't a transient outage that got patched. It's a standing gap in how failures are handled — the system doesn't distinguish between “you used the credits” and “the credits were consumed by a server error you didn't cause.”
How AIVeed Handles the Exact Same Failure Mode
AIVeed generates video through its own pipeline with automatic refund handling built in specifically for this scenario — a generation that fails for reasons outside your control shouldn't cost you anything.
“Service unavailable” still deducts credits
A server-side error with zero content generated still consumes your paid balance — confirmed twice, six months apart, on Adobe's own forum.
Technical failures are refunded automatically
If a video fails to render because of a server error, timeout, or provider-side failure — the same category as the “service unavailable” bug above — your credits are returned to your account automatically, without a support ticket. (Content blocked by moderation follows a separate policy, not this one.)
Reported bug, unresolved for six-plus months
The gap between the failure and any real fix leaves the user bearing the cost of every retry in the meantime.
Refund happens the moment failure is detected
The refund isn't a manual support escalation — it's a built-in check tied directly to the generation pipeline, so you don't need to depend on a bug ever being individually triaged and fixed.
You Only Pay for Videos You Actually Get
Frequently Asked Questions
Does Sora 2 refund credits when a generation fails?
A documented bug report on Adobe's community forum shows credits deducted on a “service unavailable” error with no video produced, confirmed as still occurring more than six months after it was first reported. Note that OpenAI is sunsetting the Sora API on September 24, 2026, so this specific Firefly integration path is going away on that date regardless. Check the platform you're using directly for its current refund policy on failed generations.
What should I do if an AI video platform charges me for a failed generation?
Screenshot the error message and your credit balance before and after, then file a support ticket referencing both. If the platform has a public bug-tracking or community forum, check whether the issue is already reported — a documented pattern strengthens a refund request.
Is there an AI video generator that automatically refunds failed generations?
Yes — AIVeed automatically returns credits when a generation fails due to a technical error, timeout, or provider-side failure, without requiring a manual support request. Content rejected by moderation follows a separate, published policy rather than this automatic technical-failure refund.
Pay for Videos, Not Server Errors
200 free credits via Google sign-up. Every failed generation is refunded automatically — no ticket required.
Try AIVeed FreeNo credit card required. Sign up with Google and generate your first video in under a minute.