A run will not start or its cost is unclear

Read the actual refusal before changing settings. A missing permission, a spending ceiling, an unsupported node and an already running job require different responses.

Symptom	Meaning and recovery
Tool missing from discovery	The key’s permissions or account visibility may exclude it. Review the key in the API panel; do not invent another endpoint.
Insufficient balance	Compare billing_status with the quote. Obtain sufficient balance or choose a smaller accepted task.
The price or plan changed and the action was refused	Read the updated estimate. The refused action is stopped before reservation and generation; choose explicitly whether to start it again. There is no paid automatic retry at the new price.
Refresh prices is shown	This tab’s compiled price list differs from the server’s current list. Use Refresh prices to reload the studio, then inspect the new estimate. Paid calls stay blocked until the pricing versions match.
Key spending limit reached	The key’s cap is separate from account balance. Review that key’s limit in the API panel.
Run estimate exceeds max_cost_usd	The plan is refused before requests begin. Quote the intended plan and agree any higher ceiling explicitly.
Human-edit warning	The plan can replace reviewed work. Inspect and resolve the warning before accepting it.
Unsupported graph node	Check the node reference. Use its supported browser or individual-tool workflow.
busy	Follow the active run or wait for the indicated interval.
Network response lost	Check existing runs/jobs and materials before sending a second operation.
Stopped run with a later charge	Submitted generation can finish after stopping. Check the job and billing records.
not_saved	Work may have been charged without updating the graph. Preserve the result and follow cache recovery.
A top-up request did not change the balance	A request is not a completed payment or credit. An administrator currently adds funds; inspect the transactions or follow the displayed contact action.
A top-up did not upgrade the plan	Start, Pro and Ultra are currently assigned by an administrator. There is no automatic top-up qualification. Ask the administrator to check the assignment and its term.

Use billing_history to investigate recorded costs and read_run_history to see which node work occurred. billing_active: false is different from an active account with zero balance. An estimate can be a ceiling with measured cost settled later.

Reconcile the quote with the charge

Check the same model, mode, quality, duration, resolution, audio and inputs when comparing prices. Start, Pro and Ultra are account plans, not model quality levels. The public calculator shows all three plan prices for one configuration; the studio uses your active account plan. See account, sign-in and credits to inspect the plan and its end date.

For a generation accepted under the current commercial policy, the agreed price is saved with its reservation. A later change to the price list or account plan does not reprice that generation. The final charge cannot exceed its reserved ceiling; measured use can make it lower. Work already pending from before the policy’s introduction keeps its earlier billing agreement rather than being silently recalculated.

If a price-change refusal appears during a multi-step run, inspect the already completed and submitted steps before retrying. Refusing the next action does not cancel earlier work. Ask an agent for a fresh quote and review the returned price before authorizing another paid action.

Purchased balance does not expire. A missing top-up or a changed free grant is a different issue: compare the transaction history with what was actually credited. Do not infer an expiry or duplicate the payment request from an unavailable report alone. Subscription private-access requests do not create a paid subscription or add a quota.

Stopping a run prevents new requests; it does not reverse already submitted work. Do not promise a refund or a free retry from the run status alone. See recover a run.

When asking for help, provide the affected node, run/job identifiers, status, time and the visible refusal. Keep API keys out of the report. State whether a material exists and whether it reached the graph, rather than reporting only “generation failed.”

Last source review: 18 October 2026. Recorded run, job and billing outcomes take precedence over assumptions based on a single response. The commercial ceiling applies to generations accepted under that policy; this guide does not establish a refund for a particular failed run.