Usage and limits
Inspect recorded runtime, model activity, balances, and plan requirements.
Use Settings → Usage & limits for the current billing period's known sandbox usage and plan information. Use Settings → Governance → Model usage for model activity and the sessions behind it.
Read sandbox usage
The usage view reports known usage, billable runtime, and sessions metered for the displayed period. It uses billable sandbox runtime while a machine is attached to a session. Paused and stopped time is excluded from that runtime view.
Machine size affects the rate through its multiplier. Runtime hours and size-weighted billable hours can therefore differ. Inspect the rate and calculation shown by the page rather than multiplying by an assumed price.
If the page says Usage history is incomplete, the total excludes earlier runtime that cannot be assigned to the billing period. It is not a final invoice and should not be treated as a complete cost audit.
Read model activity separately
Model usage shows started turns by model and teammate, daily trends, and linked session rows. Choose a time range and teammate filter before comparing results.
Turn counts and elapsed time are not the same as a final monetary charge. Model accounting and provider limits can differ by connection. Review current balances and provider state when investigating spend or a blocked run.
Understand limits
The plan and billing state can control admission to new work. Model policy, provider limits, and available execution capacity can also affect whether work starts. Read the specific requirement shown by the app; do not assume a queued session is out of credits.
For repeated or parallel work, inspect the number of routines and sessions you have active. Pausing a routine stops future automatic triggers; inspect an already accepted session separately.
Investigate an unexpected total
Check the billing period, machine size, session links, model usage, and any incomplete-history notice. Keep relevant session and billing references when asking for help. Avoid sending secret values or payment details.
See plans and wallet, machines, routines, and recovery.