Skip to content

Not Applicable For Deployment Type

URI: https://docs.ankatech.co/errors/not-applicable-for-deployment-type
HTTP Status: 409 Conflict

When you see this

You attempted to write a platform setting that is gated on the deployment model and is not applicable to this deployment. The gate runs before any scope-specific check, before any secret is sealed, and before any override is applied, so nothing was written and no change was propagated.

Common Causes

  • Writing a SaaS-only setting — rapidapi.proxy-secret is the one the catalog gates today — on a deployment that is not SAAS.
  • A console or script that surfaces the full setting catalog without honouring the applicability flag each read already carries.

Response Example

{
  "type": "https://docs.ankatech.co/errors/not-applicable-for-deployment-type",
  "title": "Not Applicable For Deployment Type",
  "status": 409,
  "detail": "This setting is not applicable to the current deployment type",
  "instance": "/api/v3/admin/platform/settings/rapidapi.proxy-secret",
  "timestamp": 1730000000,
  "extensions": {
    "requestId": "550e8400-e29b-41d4-a716-446655440000"
  }
}

Content-Type: application/problem+json — the response follows RFC 9457 Problem Details.

How to Resolve

  1. Read the setting first: every read surfaces the same deployment-type applicability the write enforces, so an inapplicable setting is identifiable before you attempt to write it.
  2. Do not write the setting on this deployment — it has no meaning here and the value would never be consumed.
  3. If the capability behind the setting is one you need, it belongs to a different deployment model; raise it as a deployment question rather than a settings one.

For full schema definitions, examples, and interactive testing, see the Developer Hub Reference.