簡単スタートを目指す

やってみたいこと！誰でも簡単にスタートするためのお手伝い！パソコン、スマホ、SNS、生成AI、新社会人！基本過ぎて聞きたくても聞けないことに注目します！

【Sora2 Issue】Web Version Can’t Generate Videos — “High Load” Errors & Possible Phone Verification Limits

動画生成AI Sora Sora 2 Released!?

Last updated:

[Sora2 Issue] Why Videos Fail to Generate on the Web Version — “High Load” Errors & Possible Phone Verification Limits

This is a quick, real-world report based on what I personally observed while using Sora2 (Web + Android app).
As of now, OpenAI has not clearly labeled this as a public “outage,” so I’ll separate what actually happened from what may be happening (hypotheses).

TL;DR: This looks like more than “server congestion” — throttling/controls may be involved

When trying to generate a video on Sora2 Web, a message like the following can appear and the job won’t start:

“We're under heavy load. Please try again in a few minutes.”

At first glance, this seems like simple congestion. However, in my tests it behaved inconsistently: sometimes it worked, sometimes it didn’t — and in some cases the result differed by account even under the same device/network. That pattern suggests a mix of load plus some form of account/phone-verification-level control.

What I observed (facts)

1) Web version: “Works sometimes, fails sometimes”

  • Even in the same time window, it can pass or fail with no clear reason.
  • The most common blocker is the “High load” message.
  • Waiting “a few minutes” doesn’t always help — sometimes it stays blocked.

2) Web version: Account-dependent behavior

  • On the same device and connection, one account could generate while another could not.
  • This didn’t feel like a simple “Plus users can / free users can’t” split.

3) Web version: “3 videos at once” seems to increase failure rate (one possible trigger)

  • On Web, some users see an option like “1 video / 2 videos / 3 videos” from a single prompt.
  • In my tests, using 3 simultaneous videos made failures more likely.
  • Switching back to 1 video sometimes improved success.

Important: “3 videos at once” is not the whole story. I treat it as one factor that can raise load and trigger limits.
The bigger signal is that the same environment can behave differently across accounts.

4) Android app: In some cases it worked even when Web failed

  • I saw cases where an account that failed on Web could still generate via the Android app.
  • I also observed at least one case where a non-verified account could generate on Android.
  • iPhone is not confirmed yet.

What may be happening (hypotheses): phone-number-level throttling/controls

This section is speculation based on patterns. I can’t prove it — but it explains the behavior better than “congestion only.”

Hypothesis A: Limits may apply at the phone-number verification level (not just per account)

If controls are attached to the verified phone number, it could explain why:

  • Account A works while Account B fails under the same device/network.
  • Plus status doesn’t neatly predict success.
  • Recent changes around phone verification coincide with unstable behavior.

Hypothesis B: Multiple accounts under the same phone number may be more likely to be throttled

If a single phone number is associated with multiple accounts, the system may interpret that cluster as higher demand, increasing the chance of throttling (especially during peak load).

Hypothesis C: Hidden daily/rolling quotas may exist

The “try again later” pattern can also happen if there are daily or rolling usage limits that aren’t visible in the UI. That would explain why results vary by time of day and why it sometimes “magically” works later.

Practical workarounds (what you can do right now)

If the cause is server-side throttling, there’s no guaranteed “fix” on the user side. Still, these steps improved my success rate:

1) Avoid “3 videos at once” for now

  • Set generation to 1 video when possible.
  • 3 simultaneous videos may push you into a failure/limit zone during load spikes.

2) Change the time of day (avoid peaks)

  • Waiting “a few minutes” isn’t always enough; try later (or off-peak hours).
  • Success rates often shift depending on demand waves.

3) If Web fails, try the Android app

  • In my tests, Android sometimes succeeded when Web didn’t.
  • This suggests different routing, throttling rules, or rollout states between platforms.

4) Don’t spam retries

  • Rapid repeated attempts can backfire if throttling is in play.
  • Space out retries and keep changes minimal (1 video, same prompt, later time).

Will this be “unlocked” eventually?

OpenAI has not provided a clear public schedule for changes here. However, the message language (“high load”) strongly suggests temporary throttling rather than a permanent block.

  • If it works later: likely congestion/rolling limits.
  • If only specific accounts fail: phone verification or account-level controls may be involved.
  • If it stays broken for days: consider platform switching (Android), changing environments, or contacting support.

This happened before on Sora1 as well (historical context)

Similar patterns (time-based failures, transient errors, platform differences) appeared during Sora1. So while this is frustrating, it’s not unprecedented for the Sora ecosystem to experience load waves and temporary instability.

Summary (my current conclusion)

  • Sora2 Web can fail to generate with a “High load” message.
  • The behavior looks inconsistent, sometimes account-dependent.
  • This suggests not only congestion but potentially phone verification (phone-number-level) throttling.
  • “3 videos at once” may be one trigger that increases failure rate (a contributing factor, not the only cause).
  • For now: use 1 video, retry later, avoid spam, and try Android if Web is blocked.

This is a developing situation. I’ll update this post if the behavior changes or if official information appears.

Related links (my tests / related posts)

Related links (official / past posts / more)

 

X (Twitter): https://x.com/Kantanstart
Instagram: https://www.instagram.com/kantanstart