Limits and budget

"Review held"

A Review held notice can mean uncertain earlier API usage or an exhausted spending cap. Known spend and retained exposure both matter; missing usage is not zero. A developer should not submit repeated requests to clear a financial hold.

The maintainer inspects the specific retained request and its evidence. Accepting an upper-bound exposure is not settling a charge, making a run complete or raising the cap. The operator may reconcile it or record a permitted request-specific continuation decision. Pending work can resume when its admission blockers clear; a hold is not permission to replay a previously started model call or review POST.

Waiting for a subscription window

Claude and ChatGPT subscription stages can report a usage window. A recorded reset within Sigma's supported waiting window, with waiting enabled and its retry limit not reached, lets the affected job wait for automatic resumption. The status names the provider and displays the reset in UTC. A scheduled resumption does not prove the provider will then accept work.

An unknown or distant reset can leave that run unfinished instead. Follow its recorded recovery guidance. The maintainer may need to restore or replace the installation's login, or arrange an available API reviewer. Changing execution paths requires the repository's permitted configuration; the Automatic / On request / Off controls only change the schedules of already configured reviewers. An explicit selector cannot bypass an absent API reviewer, private-repository gate or Off mode.

What the maintainer can do

• Inspect the recorded cause, job and request before deciding what to change.
• For an API hold, ask the operator to reconcile the request or record the authorized continuation/cap decision. The UI does not settle charges.
• For a temporary pause, runtime or GitHub API limit, wait for recovery or the recorded reset. No provider-wide readiness is inferred from one job.
• For a subscription refusal, use the run's repository settings link and confirm the permitted execution configuration with the maintainer. A link to settings does not prove a roster-change control exists.
• Set a configured reviewer to On request or Off to stop future automatic admissions. Already accepted jobs may still finish and history remains.

Per-installation quotas

Not yet available. This source baseline does not establish a per-customer review allowance, paid plan, overage rule or per-connection invoice accounting. The operator's API spending cap is different from a provider subscription's usage window and from a future product quota. Proposed review counts or discounted rechecks are product decisions, not limits to display as active.

Changing source or a default does not activate a new live spending cap. Read the installation's recorded effective policy; quota, payer and invoice UI require their own accepted backend and financial lifecycle.