MAJORFailure Reference

Sora Camera Control Failure — Refund Guide

Technical Classification

Camera Conditioning Bypass

Camera Conditioning Bypass on Sora occurs when the camera-motion conditioning channel is down-weighted relative to the subject prompt during generation. Sora encodes camera instructions separately from subject prompts; under certain prompt structures (especially when the subject prompt is long or visually complex) the camera channel can be effectively ignored. Result: you ask for a dolly-in and get a static medium shot.

How to identify this failure

✕Prompt asks for dolly-in, output is locked-off static
✕Prompt asks for orbit, output is a pan or no motion
✕Camera motion magnitude is smaller than requested
✕Camera motion direction is wrong (left instead of right)

Real generation examples

Prompt used

"Slow dolly-in to a chef plating a dish in a fine-dining kitchen"

Failure observed @ 0:00 → 0:05

Output is a locked-off medium shot — no dolly motion at all

Documentation strength

If you need to escalate

HIGH — OpenAI refunds Sora camera-conditioning failures on paid output with timestamp + prompt evidence.

AVA is a pre-purchase prevention tool, not a post-purchase recovery tool. Platforms generally do not guarantee credit refunds for output-quality failures; goodwill credits are at each platform's discretion. The strength rating reflects how well-formed your support ticket can be, not a promised outcome.

Prevention + documentation steps

01
Score your prompt before you generate
Run your prompt through AVA's pre-flight scoring against the Camera Conditioning Bypass pattern. Green light = generate. Yellow/red = rewrite using the suggested fix before you commit credits.
02
Capture Generation ID + timestamp if it failed anyway
Find the Generation ID in the URL or share link. Note the exact time when the Camera Conditioning Bypass first appears (e.g. "failure first visible at 1.2s"). Timestamped evidence is significantly stronger than a general complaint.
03
Use the correct technical term in your support ticket
Describe this failure as "Camera Conditioning Bypass". This term maps to a recognised internal workflow in the support system and routes the ticket to the right team.
04
Submit via the correct support channel
Runway has no direct email intake. Pro+ plan: open the in-app AI Assistant (help widget bottom-right of app.runwayml.com), describe the failure with the technical term, attach evidence. Free/Standard plan: human support isn't available — your channel is Discord #community-help with @On Call - Moderators.

Frequently asked questions

Does OpenAI refund Sora credits for ignored camera motion?

Yes — Sora camera-conditioning failures on paid output are honoured by OpenAI support when the prompt explicitly named the camera motion.

Why does Sora ignore camera motion?

Camera conditioning is a separate channel from the subject prompt. Under complex subject prompts the camera channel can be down-weighted to zero effective influence.

How do I make Sora respect camera motion?

Put the camera motion FIRST in the prompt before subject. Use canonical cinematography terms (dolly-in, dolly-out, crane up, orbit). Avoid combining camera motion with complex subject choreography.

Score your prompt

Score your prompt against this failure mode in 30 seconds

Paste your prompt and the platform you intend to use. AVA returns a red/yellow/green score against this specific failure mode plus a concrete rewrite if the risk is high.

Install free All 105 failure modes

AVA Pro · founders' round

$50 for 6 months of unlimited scoring across all failure modes + personal failure-history dashboard. Locks in $13/mo grandfathered after.

Claim $50 founders