Execution and limits
Limits and budget
Several independent limits can stop or delay a review: your account's Sigma review units, the operator's API spending cap, a provider's subscription usage window, and GitHub's API limit for the installation. Read the cause on the check or run page before changing an account or requesting another review.
Checks and reviews in the current format (public format v2) show no money on GitHub: no amounts, budget or provider names; the run page carries the detail. Checks and reviews published before public format v2 keep their wording, including Review held and the provider name; some still show a Cost section or "API cost estimate" lines.
Account-wide review units
In Connection, the Sigma review units panel shows the current account's monthly allowance when an authoritative snapshot is available. Each reviewer uses a separate unit; two reviewers on one PR are not one unit. The allowance is shared across that account's reviewers and execution routes. Choosing a personal runner does not create a separate allowance.
- Monthly limit is the configured allowance for the current UTC calendar month.
- Available is the part not reserved or used in that snapshot.
- Reserved is held for reviews; it is not yet confirmed usage.
- Used is confirmed settled usage. It is not a count of finished reviews, and a finished, incomplete or cancelled result alone does not establish a charge.
Available, reserved and used add up to the monthly limit. As of identifies the snapshot time. Use Refresh to check again; a displayed balance is not a guarantee that a new request can start. A confirmed zero means no units are available in that snapshot. An unavailable or expired snapshot means unknown, not zero; Sigma hides its numbers instead of showing an old balance as current.
If the panel asks to check the account again, use Reload page and the existing
account connection flow. If the allowance cannot be confirmed or needs a
maintainer's attention, write to the Sigma team with the run's recorded reason
(see Access and feedback). Buying provider usage or repeating /sigma review does not repair an
account policy or accounting conflict.
The period ends at the start of the next UTC calendar month. That boundary does not guarantee renewed access or a particular next allowance: the account still needs a valid configured policy. This guide sets no allowance amount, price, invoice or rule for which review outcomes consume units.
"Review waiting": Sigma is not starting new reviews
When the operator's API budget stops new work, the review's check stays queued and says: "Sigma is not starting new reviews right now. The review starts automatically when it can; no new request is needed." GitHub does not say which of the two causes applies; Sigma's records do, and the operator can read them:
- an earlier request's cost is unconfirmed (the ledger holds a reservation nobody has settled yet);
- Sigma's review budget is used up.
Checks published before public format v2 title this Review held and name the cause.
Known spend and held exposure both count; a missing usage figure is not zero.
Repeating /sigma review does not clear a hold.
The cap is set by the operator: a lifetime amount by default, or an amount per UTC calendar month, in which case the allowance returns on the first of the next month. Subscription usage is observed outside the cap and never changes it. Accepting an uncertain exposure is a per-request decision recorded by the operator; it settles no charge, completes no run and raises no cap. Held work resumes on its own once the blocker clears.
Waiting for a subscription window
A hosted Claude or ChatGPT subscription stage can hit the provider's usage window. The following waiting rules apply to that hosted stage, not a refusal reported by a personal runner.
- When the provider reports a reset within the waiting window (6 hours by default), the job waits and resumes 60 seconds after the reset. The check reads Review waiting, says the reviewer reached its provider usage limit and shows the reset time in UTC. It does not name the provider.
- A job waits at most three times in a row; the fourth refusal ends it as Review unfinished, with the refused attempts kept in history.
- An unknown or more distant reset ends the run unfinished at once, with recovery guidance on the check.
A scheduled resumption does not prove the provider will then accept the work, and one refusal says nothing about other reviewers or other logins.
Personal runner sign-in or subscription refusal
Personal runner self-service setup and login recovery are not yet available on the hosted service. This section explains recorded device reports from a separately configured personal installation; it is not a setup or account-switching procedure.
A personal runner uses its user's own provider sign-in on that computer; it is not shared subscription capacity for other customers. If a supported personal review reports an expired sign-in or subscription limit, the run page and GitHub message name it as device-reported. Sigma has not independently checked that provider account or its remaining usage. On GitHub the check is titled Personal review stopped and says "provider sign-in" or "provider plan" instead of naming the provider.
- Expired sign-in: follow that installation's accepted local sign-in and service-recovery instructions. Keep provider credentials on that computer; do not send them to Sigma. If those instructions are unavailable, ask the Sigma maintainer before requesting another review.
- Subscription limit: check available usage on that computer. A shown UTC reset is reported by the device; if none was reported, the reset remains unknown.
This report does not schedule an automatic retry or change Sigma review units or
the operator's budget. After restoring access, check the current run before
requesting another review with /sigma review. A retained historical result is
not an instruction to repeat work that a newer run has already done.
What the maintainer can do
- Read the cause first. Open the check summary or the run page and note the job, the request and the recorded reason before changing anything.
- Not starting new reviews, unconfirmed cost (Review held on older checks): ask the Sigma team to reconcile that request or record a continuation decision that retains the exposure. The web pages do not settle charges; buying more review units does not resolve this hold.
- Not starting new reviews, exhausted budget: ask the Sigma team to raise the cap or wait for the next calendar month if the cap is monthly.
- Waiting for any other reason: follow the recorded reason. GitHub limits may have a reset time; a pause or runtime outage needs operator recovery. Repeated GitHub commands do not remove those blockers. A hosted subscription window resumes within the rules above; a personal-device refusal does not schedule that retry.
- Review refused: the check says only that the reviewer is not enabled for this repository. Confirm with the operator which execution paths this repository is permitted; the modes on the settings page change schedules, not executors.
- Stop future work: set a reviewer to On request or Off. Jobs already accepted may still finish; history stays.
For operators. The cap and its period are set with a budget receipt (
set_cap, lifetime or UTC calendar month; the configured default is a lifetime amount). The operator can reconcile a hold or accept its retained exposure for continuation. Acceptance does not settle or release that exposure. The waiting window isSIGMA_PROVIDER_WINDOW_WAIT_SECONDS(default 21600). See the runbooks for each procedure.