Start free →

Error codes

Budgets, plan limits and public systems

Each code of this family: what it means, its most frequent cause, what to do and who can do it.

All error codes

budget_exceeded

What it means
This call was blocked before any spend: a budget is used up.
Most frequent cause
The budget “‹budget›” has reached its limit for this period.
What to do
Ask the budget’s owner to raise the limit, or wait for the next period.
Who can do it
An owner or admin of the workspace · Open the screen

budget_unavailable

What it means
This call was blocked: the budget check could not run.
Most frequent cause
When Azoth cannot check the budget, it blocks the call rather than risk unchecked spend.
What to do
Try again in a moment. If it keeps happening, tell your administrator.
Who can do it
Azoth, or the operator of this deployment

ai_ops_limit_exceeded

What it means
This call was blocked: the plan’s monthly AI operations are used up.
Most frequent cause
Your workspace’s plan includes a monthly number of AI operations, and it has been reached.
What to do
An administrator can upgrade the plan; otherwise the quota resets next month.
Who can do it
An owner or admin of the workspace · Open the screen

sealed_decisions_limit_reached

What it means
This call was blocked: the plan’s sealed decisions for this month are used up, and the grace period has ended.
Most frequent cause
Past the plan’s monthly sealed decisions, calls stay served and sealed for a grace period; it has ended, so calls past the quota are refused — and each refusal is sealed too.
What to do
An administrator can move to a larger plan (Settings › Organization); otherwise the quota resets next month.
Who can do it
An owner or admin of the workspace · Open the screen

governed_system_limit_reached

What it means
Every governed system your plan allows is in use, so a new one cannot start.
Most frequent cause
A system or an agent was declared or activated while all the places of the plan were taken.
What to do
Move to a larger plan from the pricing page, or stop or end a system to free its place. Systems in service keep running.
Who can do it
An owner or admin of the workspace · Open the screen

billing_cancel_failed

What it means
A workspace is deleted, or erased with its owner’s account, only once its subscription is cancelled. That cancellation failed, so nothing was deleted.
Most frequent cause
A brief problem reaching the payment provider, or billing not configured on this deployment.
What to do
Nothing was deleted: the workspace’s subscription could not be cancelled first. Try again in a moment; if it keeps failing, cancel the subscription in Settings › Organization (Manage billing), then delete again, or contact support.
Who can do it
An owner of the workspace · Open the screen

subscription_exists

What it means
A workspace has one subscription at a time. This one already has one that bills, or can bill again once its payment is settled, so a second checkout is not opened.
Most frequent cause
A plan change asked through checkout while a subscription is active or in trial, or a trial that ended without payment whose subscription still awaits it.
What to do
This workspace already has a subscription — active, in trial or awaiting payment. Manage it in the billing portal: change the plan there, or update the payment method to settle what is due. A second subscription is never opened beside it.
Who can do it
An owner or admin of the workspace · Open the screen

plan_required

What it means
This feature runs on this deployment, but the workspace’s plan does not include it.
Most frequent cause
The workspace is on a plan below the one the answer names (requiredPlan).
What to do
Compare the plans on the pricing page, then move to the plan named — from Settings › Organization for Starter or Growth, with our team for Enterprise. Nothing else changes until then.
Who can do it
An owner or admin of the workspace · Open the screen

regression_suite_limit_exceeded

What it means
The workspace has as many regression suites as its plan allows, so a new one cannot be created.
Most frequent cause
A suite created while every suite of the plan was in use.
What to do
Your plan’s regression suites are all in use. Delete a suite you no longer run, or move to a larger plan (Settings › Organization).
Who can do it
An owner or admin of the workspace · Open the screen

exhaustion_slow

What it means
This call was slowed down: this visitor sends too many requests.
Most frequent cause
The system is public, and one of its visitors went past the calls a minute its profile allows.
What to do
Wait a minute and try again. If the volume is legitimate, an owner or admin raises the threshold on the system’s page.
Who can do it
The developer of the calling code · Open the screen

exhaustion_challenge_required

What it means
This call waits for a check: the system sees unusual volume.
Most frequent cause
The system is public, and the volume of this visitor, or of the whole system, went past what its profile allows without a check.
What to do
Have the visitor pass the challenge on your site (a captcha), then resend the call with the X-Azoth-Challenge-Passed header.
Who can do it
The developer of the calling code · Open the screen

exhaustion_blocked

What it means
This call was blocked: unusual volume on a public system.
Most frequent cause
This visitor, or the whole system, went far past the volume its profile allows; the pause lifts on its own once the volume is back to normal.
What to do
Wait, then try again. An owner or admin sees the attack in « Waiting for you » and decides whether to stop the system.
Who can do it
An owner or admin of the workspace · Open the screen

exposure_unavailable

What it means
Exposing a system to the public is not available on this deployment yet.
Most frequent cause
On Azoth’s service, an update not applied yet. On a deployment of your own, its operator has not applied the latest database updates.
What to do
Exposure to the public is not available on this deployment yet.
Who can do it
Azoth, or the operator of this deployment

exhaustion_incident_not_found

What it means
This exhaustion incident does not exist in this workspace.
Most frequent cause
A link from another workspace, or an id typed by hand.
What to do
This exhaustion incident does not exist in this workspace.
Who can do it
Any member of the workspace

own_ai_busy

What it means
Azoth’s own AI is paused for now.
Most frequent cause
Azoth reached the spending it allows its own AI for today, or saw an unusual volume of calls to it.
What to do
The assistant keeps answering from what Azoth records, without a model. Try again later.
Who can do it
Azoth, or the operator of this deployment

ingest_queue_full

What it means
Azoth’s ingest queue is full: the batch was not accepted, and nothing was stored.
Most frequent cause
Processing is behind — a burst of events, or a slow database. The answer’s retryAfterMs says when to send the batch again.
What to do
The ingest queue is full and this batch was not stored. Send it again after the delay the answer gives (retryAfterMs).
Who can do it
The developer of the calling code

workspace_limit_reached

What it means
You own as many workspaces as your plan allows, so this one was not created.
Most frequent cause
The plan’s limit of workspaces is reached.
What to do
Delete a workspace you no longer use, or move to a larger plan (Settings › Organization).
Who can do it
An owner of the workspace · Open the screen

agent_limit_exceeded

What it means
Every agent your plan allows is in use, so this one was not created.
Most frequent cause
The plan’s limit of active agents is reached.
What to do
Archive an agent you no longer run, or move to a larger plan (Settings › Organization).
Who can do it
An owner or admin of the workspace · Open the screen

workflow_limit_exceeded

What it means
Every workflow your plan allows is in use, so this one was not created.
Most frequent cause
The plan’s limit of workflows is reached.
What to do
Delete a workflow you no longer use, or move to a larger plan (Settings › Organization).
Who can do it
An owner or admin of the workspace · Open the screen

connector_limit_reached

What it means
Every connector your plan allows is in use, so this one was not added.
Most frequent cause
The plan’s limit of connectors is reached.
What to do
Remove a connector you no longer use, or move to a larger plan (Settings › Organization).
Who can do it
An owner or admin of the workspace · Open the screen

simulation_quota_exceeded

What it means
The simulations your plan allows this month are used up.
Most frequent cause
Many simulations run this month.
What to do
Wait for next month’s allowance, or move to a larger plan (Settings › Organization).
Who can do it
An owner or admin of the workspace · Open the screen

plan_feature_required

What it means
Single sign-on is part of the Growth and Enterprise plans.
Most frequent cause
The workspace is on a plan without single sign-on.
What to do
Move to Growth in Settings › Organization, or ask our team about Enterprise.
Who can do it
An owner or admin of the workspace · Open the screen

audit_export_not_entitled

What it means
The continuous audit export is not included in this workspace’s plan.
Most frequent cause
The workspace is on a plan without the audit export.
What to do
Move to a plan that includes the audit export (Settings › Organization).
Who can do it
An owner or admin of the workspace · Open the screen

sovereign_routing_required

What it means
Sovereignty insights are not included in this workspace’s plan.
Most frequent cause
The workspace is on a plan without sovereign routing.
What to do
Move to a plan that includes sovereign routing (Settings › Organization).
Who can do it
An owner or admin of the workspace · Open the screen

plan_insufficient

What it means
Inventory Object ingestion is not included in the Free plan.
Most frequent cause
The workspace is on the Free plan.
What to do
Move to a paid plan in Settings › Organization, then run the test again.
Who can do it
An owner or admin of the workspace · Open the screen

checkout_required

What it means
The Growth trial starts at checkout, with a payment method — not from here.
Most frequent cause
A Growth trial asked for without the checkout.
What to do
Choose Growth in Settings › Organization and complete the checkout.
Who can do it
An owner or admin of the workspace · Open the screen

no_trial

What it means
No trial is waiting for this workspace.
Most frequent cause
A trial used already, a plan chosen without one, or a workspace already paid for.
What to do
Choose a plan in Settings › Organization.
Who can do it
An owner or admin of the workspace · Open the screen

annual_price_unavailable

What it means
Yearly billing is not offered for this plan, so no checkout was opened.
Most frequent cause
This plan is billed monthly only.
What to do
Choose monthly billing for this plan, or ask our team about a yearly contract.
Who can do it
An owner or admin of the workspace · Open the screen

not_in_deployment

What it means
Billing is not part of this deployment: this address receives nothing.
Most frequent cause
A deployment of your own takes its plan from its licence.
What to do
Nothing to do: only Azoth’s service receives billing events.
Who can do it
Azoth, or the operator of this deployment

entitlement_unavailable

What it means
The plan’s limits could not be read, so nothing was started.
Most frequent cause
A brief database problem.
What to do
Try again in a moment.
Who can do it
Azoth, or the operator of this deployment

simulation_access_unavailable

What it means
Access to simulations could not be checked, so none was run.
Most frequent cause
A brief database problem.
What to do
Try again in a moment.
Who can do it
Azoth, or the operator of this deployment

mandate_spend_unavailable

What it means
Spend per mandate is not available on this deployment yet.
Most frequent cause
On Azoth’s service, an update not applied yet. On a deployment of your own, its operator has not applied the latest database updates.
What to do
Contact support or the operator of this deployment.
Who can do it
Azoth, or the operator of this deployment

month_cap

What it means
This campaign’s cap would take the workspace past its monthly red-teaming cap, so it was not started.
Most frequent cause
Campaigns already run this month, or a campaign cap set high.
What to do
Lower the campaign’s cap, wait for next month, or raise the monthly cap in the red-teaming settings.
Who can do it
An owner or admin of the workspace · Open the screen

billing_managed_by_sales

What it means
This workspace’s plan is billed under a contract with Azoth, not through the online checkout.
Most frequent cause
An Enterprise workspace asking for a checkout.
What to do
This workspace’s plan is billed under a contract. Contact Azoth’s sales team to change it.
Who can do it
An owner of the workspace · Open the screen

billing_account_missing

What it means
This workspace has no billing account yet, so there is no billing portal to open.
Most frequent cause
The workspace has never been billed for a paid plan.
What to do
This workspace has no billing account yet. Choose a plan first: the billing portal opens once the workspace is billed.
Who can do it
An owner or admin of the workspace · Open the screen

entry_limit_reached

What it means
This list holds as many entries as it can, so the new one was not added.
Most frequent cause
The IP allowlist’s largest number of entries is reached.
What to do
This list is full. Remove an entry, or use a broader one (a CIDR range), before adding another.
Who can do it
An owner or admin of the workspace