Reference
Error codes The AMICU-* diagnostic catalog, with meaning and fix.
Diagnostics have the form AMICU-<CATEGORY>-<NNN>. The category is the fastest triage signal. Only diagnostics with severity error fail a command; warnings and info are advisory.
Category Meaning PARSEHCL syntax SCHEMAMissing, unknown, or duplicate fields and ids REFReference to a resource that does not exist CAPRuntime, artifact, or hardware capability mismatch MEMModel does not fit POLICYResidency, governance, secrets, endpoint keys STATEState lock, corruption, or backend PROVIDERProvider availability, credentials, catalog
Code Severity Meaning Fix AMICU-PARSE-001error An HCL block is not closed Close the block, then amicu fmt AMICU-PARSE-002error The HCL text is not syntactically valid Read the message for the location and fix the syntax
Code Severity Meaning Fix AMICU-SCHEMA-001error A required attribute is missing Add the field named in the message AMICU-SCHEMA-002error The same resource id is declared more than once Rename or remove the duplicate; ids are unique per kind across all files AMICU-SCHEMA-003error Unknown attribute or block, usually a typo Use the suggested name. env {} and labels {} accept any key.
Code Severity Meaning Fix AMICU-REF-001error A reference points at an id no resource declares Correct the <kind>.<id>.id expression or add the resource
Code Severity Meaning Fix AMICU-CAP-001error The runtime cannot serve the artifact (llama.cpp needs GGUF) Change the runtime or artifact AMICU-CAP-002error An extra_args flag duplicates a typed field's flag Use the typed field AMICU-CAP-003error An extra_args flag or env key is denylisted Remove it. Use api_key for keys. AMICU-CAP-004info extra_args is non-empty, so the memory fit result is unverifiedCheck real memory use AMICU-CAP-005error chat_template and chat_template_file are both setSet one AMICU-CAP-006warning GGUF artifact on vLLM (experimental upstream) Use safetensors, or accept the risk AMICU-CAP-007error A speculative draft model is the deployment's own model Reference a different model AMICU-CAP-008error Invalid scaling {} values See deployment for the allowed ranges AMICU-CAP-009error scaling {} on a provider with no scaling supportRemove the block or use a provider with scaling support (Modal today) AMICU-CAP-010warning vLLM KV cache not estimated; the model has no n_layers, n_kv_heads, head_dim Declare the shape on the model
Code Severity Meaning Fix AMICU-MEM-001error The model does not fit in available VRAM or memory Smaller quantization, shorter context, or bigger hardware AMICU-MEM-002error A single artifact file exceeds available memory A smaller variant or different hardware
Code Severity Meaning Fix AMICU-POLICY-002error A region violates the residency or allowed-regions policy, or a deny rule. Also reported when a secret("NAME") variable is not set at apply time. Change the region, or set the environment variable named in the message AMICU-POLICY-003error A provider is not allowed, or is denied Change the provider or the rule AMICU-POLICY-004error A secret-designated field was given as a literal Use secret("NAME") AMICU-POLICY-005warning A free-text field or comment looks like a secret Remove it, or add # amicu:allow on the line AMICU-POLICY-006warning A runtime env value looks like a secret Use a secret(...) reference AMICU-POLICY-007error An off-machine deployment has no api_key Add api_key = secret("NAME") and export NAME AMICU-POLICY-008error The resolved key is unusable: empty, or has a comma, whitespace, or non-ASCII characters Regenerate it, for example openssl rand -hex 32
AMICU-POLICY-001 (budget exceeded) is defined but budgets are not enforced. These codes exist in the shared catalog and in the server and provider libraries. The amicu CLI does not emit them today; they are listed so you can recognize them in server output. The CLI reports state-lock and provider failures as plain error: messages instead.
Code Severity Meaning AMICU-POLICY-001error A deployment exceeds a configured budget AMICU-POLICY-010error A referenced secret is unavailable AMICU-POLICY-011error The secret backend does not support the requested operation AMICU-POLICY-012error The secret backend failed transiently
Code Severity Meaning Fix AMICU-STATE-001error State is locked by another operation Wait, or pass --lock-timeout AMICU-STATE-002error A push or rollback was attempted without holding the lock Take the lock first AMICU-STATE-003error Recorded state is corrupt Manual recovery; see State and backends AMICU-STATE-004error The requested history version does not exist Pick an existing version AMICU-STATE-005error The state backend's storage failed (connectivity, driver) Check the backend and retry
Code Severity Meaning Fix AMICU-PROVIDER-001error Requested capacity is unavailable in the region Try another region or GPU AMICU-PROVIDER-002error A model artifact download failed transiently; a retry resumes it Retry AMICU-PROVIDER-003warning Provider capability or pricing data is stale or could not be refreshed The last snapshot is used; refresh later AMICU-PROVIDER-010error The request names an offering the provider does not have Pick a listed offering AMICU-PROVIDER-011error The request names a region the provider does not serve Pick a listed region AMICU-PROVIDER-012error The handle refers to no known provisioned instance Re-plan AMICU-PROVIDER-013error The provider backend failed transiently Retry AMICU-PROVIDER-014error The provider rejected the credential Check the credential AMICU-PROVIDER-015error The operation is permanently unsupported by this adapter (a catalog-only provider) Use a supported provider; not retryable
Severity decides
A warning never fails a command. Resolve warnings anyway; for example AMICU-CAP-010 means the fit check ignores the KV cache.