parallel45 API error
capability_not_configured
The capability is not configured yet
Published ahead of the API. No endpoint emits this code yet — error
exits currently carry type: "about:blank". Read this as the intended contract,
not as a description of live behaviour. About this catalogue
- Problem
type - https://errors.parallel45.tech/capability_not_configured
- HTTP status
- 503
- Retryable
- No — the identical request will fail identically.
What it means
The feature exists but has no configuration or upstream capability behind it for this tenant.
Nothing failed and nothing upstream was called. The resource is real, so this is not a not-found; there is simply no mapping, instruction set or provider wired for this tenant yet.
What to do
Present it as unavailable rather than as an error, and do not retry -- retrying cannot succeed until somebody configures it. This is an operational gap, not a transient fault.
Do not confuse this with
provider_unavailable, which is the failing-dependency case and IS worth retrying. This is the third collapse P45DEV-946 named ('60 vs a genuine 503, same status and opposite retryability'). Note the two are deliberately given different statuses here as well as different codes, so the shared-503 trap that collapse describes cannot arise -- but retryability is still the distinction that matters, and it is opposite.