Factory Droid rate limit reached mid-session?

Factory uses rolling 5-hour, weekly, and monthly limits. Its documentation says the current request finishes, then later requests are refused. That makes the first job verification: determine what the finishing request actually changed.

Preserve first: Run /limits or check Settings > Usage to identify the exhausted window. Before switching tools, inspect whether the last accepted request changed files and whether a Factory Mission is paused.

Match the failure before retrying.

Standard Usage is exhausted

Run /limits or open Settings and Usage to see which rolling window is blocking the next request.

A Mission paused

Factory says Missions pause when a rate limit is hit. Do not assume the remaining plan completed.

The last request finished at the boundary

Inspect files and tests because the final accepted request can complete even though the next one is refused.

Safe recovery path.

Run /limits and identify the five-hour, weekly, or monthly window that is exhausted.

Inspect git diff, changed files, command output, and verification status from the last completed request.

Choose Droid Core, enable Extra Usage, wait for reset, or move the task to another supported AI.

Continue with a packet that names the completed work, paused work, risks, and next smallest check.

What the next AI should receive.

Factory Droid version and surface, output of /limits or the Usage screen, active rolling window, Mission status, last accepted action, current branch/diff, checks already run, and next uncompleted acceptance condition.

How ShardStitch works with Factory Droid.

ShardStitch builds the continuation state outside Factory's quota window. The packet can return to Droid Core or move cross-tool while preserving verified changes, pending work, and the exact point where the limit interrupted execution.

Source trail.

The linked Factory pricing, quickstart, and release-note pages describe rolling usage windows, the /limits control, and Mission behavior. Limits can vary with plan and product changes, so use the account display for the current window rather than copying a fixed reset estimate.

FAQ.

Does Factory refusing the next request mean the last task failed?

Not necessarily. The documentation says a request already in progress can finish before later requests are refused. Inspect the diff and acceptance checks to determine what completed.

Can /limits show whether a Mission is done?

Use /limits to inspect usage; check the Mission itself for task status. A usage window and a Mission completion state are separate facts.

Should I rerun the full Factory task after a limit reset?

First compare the branch and diff with the original goal. Continue only with the missing step, and avoid replaying completed edits.

Scope note: This guide covers a Factory usage limit reached during a coding task. It does not imply that a paused Mission completed or that every account has identical rolling limits.