TIER_UNAVAILABLE

The account's plan could not be confirmed, so the check was not run and nothing was charged. HTTP 503. Transient — retry shortly; this is never a problem with your request.

The service could not confirm what this account's plan includes, so it did not run the check. Nothing was charged and no allowance was spent.

This is not a problem with your request. The same call will succeed once the plan can be read again, and there is nothing to change in the meantime.

Tier allowances are held by the payment provider rather than in this service, so that what a plan includes and what it costs are one setting in one place. When that reading is briefly unavailable the service holds the last known numbers; this code appears only when it has no usable reading at all for the tier the account is on.

The envelope

{"ok": false,
 "error": {"code": "TIER_UNAVAILABLE",
           "message": "This account's plan could not be confirmed just now, so the check was not run. Nothing has been charged. Please try again shortly.",
           "docs": "https://docs.agents.jaxon.ai/errors/tier-unavailable.md"},
 "versions": {"...": "..."}}

The fix

• Retry after a short pause. Seconds to a minute or two. The reading is refreshed on a timer, so a retry that is too fast simply gets the same answer.
• Do not fall back to a different call. Compiling, saving and loading rulesets are unaffected and still free, so work that does not need a verdict continues normally.
• Do not retry in a tight loop. The answer does not change until the plan can be read, and a loop will not make that happen sooner.
• If it persists, get in touch with Jaxon. A reading that stays unavailable is an operator-side fault with a named product behind it, and an operator can see exactly which one from the service log.

Call GET /v1/account (or dsail_get_account_status) to see the account's position once checks are going through again.

See also: [ENTITLEMENT_EXCEEDED](entitlement-exceeded.md), Error codes.