Solved

Why did my image or video generation fail?

ToRun Team · Replies: 1 · Views: 3

I've been trying to generate images and a short video clip through ToRun for the past hour and keep hitting failures. The requests seem to go through — I see a spinner for a while — but then they either show an error message or just silently produce nothing. My text chat works fine on the same models I've been using, so this doesn't feel like a general connectivity issue.

Here's what I've tried so far:

Switched from a 1792x1024 landscape to a standard 1024x1024 square crop — same result.
Tried two different image prompts: one fairly detailed, one short and simple.
Attempted a 15-second video clip at 720p.
Reloaded the page between attempts.

A few questions I can't answer by reading the docs:

Is image/video billing different from text? I have a small wallet balance and an active Free tier session budget, but I'm not sure if media draws from the same pool or needs a separate threshold.
Are certain resolutions or durations blocked entirely, or just unavailable on some providers?
Could my prompt have triggered a safety filter without me knowing? I didn't get an explicit moderation message, just a generic failure.
Is there a way to tell whether the problem is on ToRun's end or the upstream provider's?

What are the most common causes of media generation failures and what should I check first?

1 Replies

ToRun Team ·14 Jun 2026 Solved

Great questions — media generation has a few distinct failure modes that are worth working through in order.

Insufficient funds. Image and video are billed per image or per second of video, not per token. Those rates are higher than text, so a wallet balance or Free tier session budget that covers a hundred chat turns may be exhausted after a handful of media requests. Check your wallet and session budget on the billing page before retrying. If funds are low, top up or wait for the session budget to refill.

Unsupported resolution or duration. Each provider accepts a specific set of image dimensions and video lengths. A resolution like 1792x1024 is valid for some models but not others. If the model ToRun routed your request to does not support that output size, the request fails. Try a standard resolution (1024x1024 for images; shorter durations for video) and see if routing picks a compatible model.

Moderation or safety block. Some failures surface as a generic error rather than an explicit moderation message, depending on how the upstream provider reports it. Review your prompt for content that could trigger safety filters — even indirectly — and simplify or rephrase.

Provider capacity. Occasionally a provider returns a capacity or rate-limit error. ToRun's fallback chain tries alternates, but if all capable providers are saturated at that moment, the request fails. Retrying a minute or two later usually resolves this.

For provider-side issues specifically, check the status page or retry with a different model if you have BYOK configured. See /pricing for current media rates.

Read-only on the public site

Open in the app