Owning surface
Billing and Provider VaultStart where the product already explains or controls the problem.
Support
Budget or plan limit reached
A cost or entitlement limit is not a bug, but it can feel like one if you do not know which layer is blocking progress.
Guide summary
Use this page to understand the surface before you act inside it.
Recover when execution is blocked by provider usage posture or your current product plan.
Guide type
SupportThis guide reflects the current product workflow and surface ownership.
Sections
5Summary first, then steps, mistakes, and recovery notes.
Related guides
3Written against the current product structure and core execution workflow.
Escalation rule
Use support with contextAttach the relevant run, mission, task, or artifact whenever possible.
Related action
Contact Support only after inspectionSupport is strongest when the dominant symptom is already known.
Guide section
Symptoms
These signals usually indicate this specific class of problem.
What it is
Recover when execution is blocked by provider usage posture or your current product plan.
When to use it
Use this guide when these symptoms match what you see in the product.
Where to find it
Start from the owning surface: Billing and Provider Vault.
What happens next
You narrow the problem before you retry or escalate.
Common mistake
Escalating too early without checking whether the owning surface already explains the blocker.
Related action
Open the owning surface first, then return here if the diagnosis is still unclear.
- A launch action is blocked
- A provider or billing warning appears
- The run cannot continue even though the workflow otherwise looks valid
Guide section
Likely causes
- Plan limits were reached
- Provider usage posture hit a budget guard
- BYOK billing or provider access needs attention
- The current plan does not include the requested posture or volume
Guide section
How to fix it
- Open Billing and review plan posture
- Review Provider Vault for provider-budget posture
- Reduce usage or wait for the relevant reset if applicable
- Upgrade or request plan changes when the current posture is intentionally too small
Guide section
Where to inspect next
Use the product surface that owns the problem first.
Where to find it
Billing and Provider Vault
What happens next
The owning surface should tell you whether the next move is fix, retry, continue, or support.
Related action
Move into Billing and Provider Vault now if you have not already done so.
Guide section
When to contact support
Contact support if the limit signal itself looks wrong or inconsistent with your visible plan and provider posture.
Tip
Report with the right object
A linked run or artifact is much easier to investigate than a generic support request with no runtime context.