> ## Documentation Index
> Fetch the complete documentation index at: https://docs.blujay.io/llms.txt
> Use this file to discover all available pages before exploring further.

# FEATURE_NOT_ENABLED

> Feature not enabled

| HTTP status | Retryable |
| - | - |
| `400` | No |

## What happened

The request asks for something that is not available in this context. Examples are a message effect on the first message of a new chat, a text-decoration animation, a webhook event type that cannot be subscribed to, or editing when editing is turned off for your workspace.

## How to fix it

Read `error.message` for the specific field. Remove that field or send it in a supported context. The guide for the feature lists where it is supported.

## Example response

An illustrative example. The `message` wording and the contents of `details` vary; branch on `error.code`.

```json theme={null}
{
  "status": "error",
  "error": {
    "code": "FEATURE_NOT_ENABLED",
    "message": "Feature not enabled",
    "type": "feature_gate",
    "http_status": 400,
    "retryable": false,
    "doc_url": "https://docs.blujay.io/errors/feature-not-enabled",
    "details": []
  },
  "trace_id": "trc_8f2a1c0e4b7d",
  "timestamp": "2026-10-14T17:30:48.000Z"
}
```

## Still stuck?

Email [support@blujay.io](mailto:support@blujay.io) with the `trace_id` from the error response. See [Errors](/errors.md) for the response format.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.