‘Too Soon’, ‘Too Many Requests’, ‘Busy Right Now’: The Limits That Count Clicks, Not Credits

Quick answer: Some actions are free or nearly free for you but cost the site something each time — sending a code, recognising an image, matching a voice, translating an edit, starting an ad read or a remake read. Those are limited by frequency: so many per minute, per hour, or one at a time per account. The message names the action; the fix is always to wait, from a few seconds (codes) to the top of the hour (recognition, matching). Nothing is charged and nothing is queued: the click is simply refused. This is different from the concurrency limit on generations, which queues your jobs rather than refusing them.

Still from “Rust City Knockout”, an AI short drama generated end-to-end by SceneMixer (6 characters, 1 episode) — Sample: “Rust City Knockout” — Painterly Anime, 1 episode, produced end-to-end by SceneMixer from the script · watch the episodes

Request a sign-in code twice in a row: the second is refused for a few seconds; the first is still valid.

Which actions have a rate limit

Sign-in codes: one every few seconds, a handful per hour per phone or address. Image recognition (ad photos, descriptions from images): per person per hour, plus a site-wide budget. Voice matching: per person per hour. Translated edits: many edits to translated storyboards in a short time. Ad and remake starts: per hour, and one read in progress at a time per account. Site-wide daily limit: a shared budget that, when reached, refuses until the next day; rare.

The SceneMixer episode editor: asset library on the left, the storyboard in the middle, the video preview on the right, and every segment along the bottom timeline — These limits count clicks per minute or per hour, not credits; the message tells you which, and waiting clears it.

What the messages look like

‘Too soon — wait a few seconds’, ‘Too many codes’, ‘Image recognition is busy’, ‘Too many image recognition requests’, ‘Too many voice matches’, ‘Too many edits in a short time’, ‘This ad is busy right now’, a remake that is already reading. Each one is a refusal of that click; the page state is unchanged. Every Error Message.

How long to wait

Codes: seconds; the hourly cap resets on the hour. Recognition and matching: the hour. Translated edits: minutes. Ad and remake: the read in progress has to finish, or the hour has to turn. The message does not show a timer; a retry after the stated interval works.

Not the same as the concurrency limit

Generations (sheets, storyboards, clips) are never rate-refused; beyond your concurrent-task limit they queue and start as slots free up. Rate limits are for the auxiliary actions above. Generating Many Segments at Once.

Why these limits exist

Each of these actions calls a model or sends a message at the site’s cost, with nothing charged to you. A per-person cap keeps a runaway script or a stuck button from spending that budget; the numbers are set so that normal use never touches them.

Action	Limit	Wait
Sign-in code	Per few seconds; per hour	Seconds; the hour
Image recognition	Per hour per person; site budget	The hour
Voice matching	Per hour per person	The hour
Translated edits	Per short window	Minutes
Ad or remake start	Per hour; one read at a time	The read, or the hour
Generations	Not rate-limited; queued	—

FAQ

Did the refused click cost credits?

No. Rate refusals never charge or queue anything.

I keep getting 'too many codes'.

Use the code you already received; it is valid for its lifetime. Then wait for the hour.

Is my account flagged?

No. These are ordinary counters that reset by themselves.

Can a member get higher rate limits?

The concurrency limit rises with membership; the auxiliary rate limits do not.

The remake says busy but I see no read running.

A read in progress on another device or tab; wait for it, or refresh the projects list.

Wait it out

Nothing was charged, nothing was lost.

Back to the project

Updated September 27, 2026