The Agent Memory API Errors
- reference
An explanation of error messages generated by the Couchbase Capella Management API and the Agent Memory API.
This page is for Agent Memory in Capella. For Capella operational, see Capella Operational Management API Errors.
API errors occur when a request fails to complete, typically returning standardized HTTP status codes that indicate the type and cause of the failure.
This API error reference lists:
Management API Error Messages
HTTP Status 400
Bad request.
| Code | Name | Description | HTTP Status |
|---|---|---|---|
|
|
The server cannot or will not process the request due to something that is perceived to be a client error. Check if you have provided a valid URL and all the required params are present in the request body. |
|
|
|
The request was malformed or invalid. |
|
|
|
The provided conflict resolution is not supported. Please choose a valid conflict resolution strategy for the bucket. |
|
|
|
Invalid job configuration. Action field cannot be empty, and must be one of 'backup' or 'restore'. Returned when a job is attempting to be added to a backup schedule with no action. |
|
|
|
Invalid job configuration. Source field cannot be empty, and must be one of 'manual' or 'scheduled'. Returned when a job is attempting to be added to a backup schedule with no source. |
|
|
|
Invalid job configuration. All restore jobs must have restore options set. Returned when a restore job is being added without restore options set. |
|
|
|
The day attribute is invalid. Only an integer between 0 and 6 is allowed. Returned when the day attribute to the timing struct is not an integer between 0 and 6. |
|
|
|
The hour attribute is invalid. Only an integer between 0 and 23 is allowed. Returned when the hour attribute to the timing struct is not an integer between 0 and 23. |
|
|
|
The incrementalEvery attribute is invalid. Returned when asked to create or modify a backup schedule, but the incremental value provided is not valid. Must be one of '1', '2', '4', '6', '8', '12', or '24'. |
|
|
|
The unit attribute is invalid. Must be one of 'minute', 'hourly', 'daily', or 'weekly'. Returned when the unit attribute is not one of the expected allowed constants. |
|
|
|
Unsupported type for backup schedule. The full backup type must be 'weekly'. Returned when the scheduled backup type is not 'weekly'. |
|
|
|
Invalid incremental backup interval. The minimum allowed incremental backup interval is every 4 hours. Returned when the incremental backup interval is quicker than every 4 hours. |
|
|
|
The backup retention time is invalid. Returned when the given backup retention time is not supported. |
|
|
|
Output type is not supported. |
|
|
|
Model with the given name cannot be deployed Returned when asked to deploy an unsupported model. |
|
|
|
Returned when attempting to deploy a model that is in any state other than pending. This can occur when a deploy job retries or when the model is in an invalid state. |
|
|
|
Returned when the user tries to deploy a model with security configuration that is not in healthy state. |
|
|
|
Returned when attempting to deploy a model that is in a failed state. Users cannot deploy a failed model. |
|
|
|
Returned when the user tries to pause a model that is in any other state other than healthy |
|
|
|
Returned when the user tries to update a model that is in a failed state |
|
|
|
Returned when the user tries to update a model that is not healthy or already updating. |
|
|
|
Language model can not be updated as a previous update is still in progress. Returned when the user tries to update a model that is already being updated. |
|
|
|
Model with the given kind cannot be deployed Returned when asked to deploy an unsupported model kind. |
|
|
|
Toolkit with the given type is not supported. Returned when an unsupported toolkit is specified for deployment. |
|
|
|
Returned when attempting to deploy a model using the given toolkit. |
|
|
|
The provided documentation URL is invalid or malformed. Returned when the DocumentationURL field does not contain a valid absolute URI. Ensure the URL includes a valid scheme such as 'http://'; or 'https://';. |
|
HTTP Status 401
Unauthorized.
| Code | Name | Description | HTTP Status |
|---|---|---|---|
|
|
The request is unauthorized. Please ensure you have provided appropriate credentials in the request header. Please make sure the client IP that is trying to access the resource using the API key is in the API key allowlist. |
|
HTTP Status 403
Forbidden.
| Code | Name | Description | HTTP Status |
|---|---|---|---|
|
|
Access Denied. Your access to the requested resource is denied. Please make sure you have the necessary permissions to access the resource. |
|
|
|
Access Denied. Your access to the requested resource is denied. Please make sure you have the necessary permissions to access the resource. |
|
|
|
Unable to create a project. Project count limit is reached. Please ensure to stay within the quota. If required, please create support ticket in order to increase the quota. |
|
|
|
Returned when attempting to do operations for backups but the cluster is a free tier cluster. |
|
|
|
Returned when attempting to do operations for CMEK but the cluster is a self service trial cluster. |
|
HTTP Status 404
Not found.
| Code | Name | Description | HTTP Status |
|---|---|---|---|
|
|
Organization not found. Check if the organization ID is valid. |
|
|
|
The server cannot find a project by its ID. Check if the project ID is valid. |
|
|
|
Check if the project ID is valid. |
|
|
|
Resource not Found. |
|
|
|
The requested cluster details could not be found or fetched. Please ensure that the correct cluster ID is provided. |
|
|
|
The cluster network information for the received ID could not be found. Please ensure that the correct ID is provided. |
|
|
|
The requested bucket does not exist. Please ensure that the correct bucket ID is provided. |
|
|
|
The requested backup record could not be found. Returned when the requested backup record could not be found. |
|
|
|
The requested download record could not be found. Returned when the download record cannot be found for the given ID and cluster. |
|
|
|
Unable to retrieve the backup specified. Returned when encountering an error while attempting to retrieve a backup record. |
|
|
|
Backup schedule not found. Returned when a backup schedule is not found for the bucket. |
|
|
|
Check userId is valid. |
|
|
|
Verify the provided user ID and ensure it corresponds to an existing user before attempting to delete. |
|
|
|
User not found. The system was unable to locate a user with the specified ID. Ensure that the provided user ID is correct and corresponds to an existing user. |
|
|
|
Unable to process request for key. The key requested does not exist. Please ensure the ID of the key is correct and try again. Please double-check the provided ID for the key and ensure it exists before making the request. |
|
|
|
The requested collection details could not be found or fetched. Please ensure that the correct collection name is provided. |
|
|
|
The requested scope details could not be found or fetched. Please ensure that the correct scope name is provided. |
|
|
|
Returned from the API when a database does not have an existing On/Off schedule. |
|
|
|
App Endpoint not found. |
|
|
|
Language Model with the provided ID is not deployed and could not be found. Returned when fetching a record that does not exist. |
|
|
|
A default VPC is required Returned when attempting to create a shared language model, but a default VPC is not presnet |
|
|
|
Unable to find the agent memory server deployment. Returned when the specified agent memory server deployment does not exist. Check that the agent memory server ID is valid and that the deployment exists within the specified cluster. |
|
|
|
Unable to find the agent memory server API key. Returned when the specified agent memory server API key does not exist. Check that the API key ID is valid and belongs to the specified agent memory server deployment. |
|
|
|
Returned when attempting to remove an allowed CIDR that is not present on the agent memory server allowlist. Check that the CIDR value matches an existing entry. |
|
|
|
Unable to find the integration. Returned when the specified integration does not exist. Check that the integration ID is valid and that the integration exists within the organization. |
|
HTTP Status 409
Conflict.
| Code | Name | Description | HTTP Status |
|---|---|---|---|
|
|
There is a conflict with the current state of a resource. Returned when trying to create or update a resource that already exists or has conflicting information. |
|
|
|
Cannot delete bucket as associated app service is not in healthy state. Please wait for the app service to become healthy before performing the action. |
|
|
|
Unable to add job, as it already exists and is waiting to be processed. Returned when there is already a backup or restore job with the same key in the backup config schedule. |
|
|
|
Unable to add backup schedule, as a schedule already exists for the bucket. Returned when there is already a backup schedule for the bucket in the backup config schedule. |
|
|
|
Unable to process request, as backup ID in the payload does not match backup ID in the path. Returned when asked to restore a backup and backup IDs in path and payload do not match. |
|
|
|
Returned from the API when an app service cannot be turned on because it is not currently turned off. |
|
|
|
Returned from the API when an app service cannot be turned off because it's in an unhealthy state. |
|
|
|
The App Endpoint is currently transitioning between states. Please try your request again once this transitioning has completed. |
|
|
|
Returned from the API when a database cannot be turned on because it is not currently turned off. |
|
|
|
Returned from the API when a database cannot be turned off because it's in an unhealthy state. |
|
|
|
Returned from the API when a database cannot be turned off because of upcoming maintenance. |
|
|
|
Returned from the API when a database cannot be turned off because of an active backup or restore job. |
|
|
|
Returned from the API when trying to turn off a database with memory only buckets. |
|
|
|
Returned from API when given database cannot be turned off because it has a pending redeployment. |
|
|
|
Returned from API when given database cannot be turned off because the linked app service is in invalid state. |
|
|
|
Returned from API when given database cannot be turned off because a turn on for the linked app service is queued or in progress. Retry once the app service is healthy. |
|
|
|
Returned from API when given database cannot be turned off because it Data API service is in an invalid state. |
|
|
|
Please ensure the analytics cluster is in a valid state to be turned on. |
|
|
|
Please ensure the analytics cluster is in a valid state to be turned off. |
|
|
|
The bucket has a max time to live set above 0 which is not supported by App Services. Please update the bucket to have a max TTL of 0. |
|
|
|
At least one of the collections has a max TTL set above 0 which is not supported by App Services. Please update the collection(s) to have a max TTL of 0 or unlink the unsupported collection(s). |
|
|
|
The bucket has a non-default durability level set which is not supported by App Services. Please update the bucket to have a durability level of 'None'. |
|
|
|
The App Service cannot be turned on while the cluster is in it's current state. |
|
|
|
Cannot turn off database because linked model service is in invalid state. Returned when user tries to turn off a cluster but has already a models deployed in an invalid state. |
|
|
|
Cannot deploy langauge model, resource cleanup is in progress try after sometime. Returned when user tries to deploy a model but cleanup is in progress |
|
|
|
An export for this backup cycle is already pending or being processed. Returned when attempting to export a backup whose cycle already has an export in the pending or processing state. Only one active export can exist per backup cycle; poll the existing export instead of creating another. |
|
|
|
An export for this backup cycle has already completed. Returned when attempting to export a backup whose cycle already has a complete export. Fetch the existing export to obtain a download URL, or wait for its archive to expire before exporting again. |
|
|
|
An agent memory server deployment already exists for this cluster. Returned when attempting to create an agent memory server on a cluster that already has one. A cluster can host at most one agent memory server deployment. Delete the existing deployment before creating a new one. |
|
|
|
Returned when an operation is attempted on an agent memory server deployment whose current state does not allow it. Wait for the deployment to reach a stable state (e.g. healthy or destroyed) before retrying. |
|
|
|
Agent memory server is not healthy. Allowlist changes require a deployed, healthy agent memory server. Returned when an allowlist mutation is attempted on an agent memory server that is not in the Healthy state. Wait for the agent memory server to reach a healthy state before modifying the allowlist. |
|
|
|
An Agent Memory server is associated with the cluster, please delete the Agent Memory server before deleting the cluster. Returned when attempting to delete a cluster that has an associated agent memory server deployment. Delete the agent memory server deployment before deleting the cluster. |
|
|
|
Returned when attempting to add a CIDR that is already present on the agent memory server allowlist. No action is needed. |
|
HTTP Status 412
Precondition failed.
| Code | Name | Description | HTTP Status |
|---|---|---|---|
|
|
The request precondition failed. The resource state does not meet the conditions specified in the request headers. Please Verify the precondition headers (e.g., If-Match, If-Unmodified-Since) and ensure they align with the current state of the resource. |
|
|
|
Please include the correct ETag version with the request. |
|
|
|
The ETag provided is not valid. The version of the document provided does not appear to be an integer. Please include the correct ETag version with the request. |
|
|
|
The ETag provided is not valid. Please include the correct ETag version with the request. |
|
|
|
Please retry the request. |
|
HTTP Status 422
Unprocessable content.
| Code | Name | Description | HTTP Status |
|---|---|---|---|
|
|
The server was unable to process the request because it contains invalid data. Check the request payload and ensure all required fields are valid. |
|
|
|
The server was unable to process the request because it contains invalid data. Check the request payload and ensure all required fields are valid. |
|
|
|
Retry with a description with a maximum length 256 characters. |
|
|
|
Retry with a name with a maximum length 128 characters. |
|
|
|
Please ensure that Availability Zone type is provided. |
|
|
|
Please ensure that Availability Zone type is provided. |
|
|
|
Please ensure that the provider provided is supported. |
|
|
|
Please ensure that payload or body of the request is not empty. |
|
|
|
Please ensure that a valid timezone is provided. |
|
|
|
Please ensure that server group has at least (1) node. |
|
|
|
Please ensure that server specifications provided contain services. |
|
|
|
Please ensure that the provided CIDR is valid. |
|
|
|
Please ensure that CIDR range has an IP address of the network address. |
|
|
|
Please ensure that the CIDR range is within the private ID address ranges. |
|
|
|
Please ensure that the CIDR range is unique within this organisation. |
|
|
|
Please ensure that the provided name has at least the minimum length. |
|
|
|
Please ensure that the provided cluster name does not exceed the maximum length limit. |
|
|
|
Please ensure that the cluster name only contains valid characters when creating or modifying the cluster name. |
|
|
|
Please ensure that the provided cluster description does not exceed the maximum length limit when creating or modifying the cluster. |
|
|
|
Please ensure that the provided region is supported by the given cloud provider. |
|
|
|
Please include the data service in the cluster specifications when creating or modifying the cluster. |
|
|
|
Please provide a valid project ID when creating a new cluster. The provided project does not exist. |
|
|
|
Please provide a valid tenant ID when creating a new cluster. The provided tenant does not exist. |
|
|
|
Please provide a valid image name when performing an operation on the cluster. The provided image name is not valid. |
|
|
|
Please provide a valid package type when creating or modifying a cluster. The provided package type is not valid. |
|
|
|
Please provide a supported provider when creating a cluster. The provided provider is not supported. |
|
|
|
Please provide a valid instance type when creating or modifying a cluster's specifications. The provided compute type is invalid. |
|
|
|
The tenant is not able to create a new cluster due to payment issues or revoked activation. |
|
|
|
The requested action is not supported for the cluster's architecture. Please ensure the cluster architecture supports the action. |
|
|
|
Please do not specify IOPS for this disk type when attempting to deploy a cluster. |
|
|
|
Please do not specify disk size or IOPS for this disk type when attempting to deploy a cluster. |
|
|
|
Please provide a valid Couchbase Server version when creating a cluster. The provided server version is not supported. |
|
|
|
Please provide a valid projectId. |
|
|
|
Please check the expiry for the allowlist. |
|
|
|
Please specify start time less than 30 days ago. |
|
|
|
Please specify start time more than 15 minutes ago. |
|
|
|
Please ensure start time is before end time. |
|
|
|
Please specify time range that is more than 15 minutes. |
|
|
|
Please provide a valid sort direction ('asc' or 'desc') when using the 'sortDirection' parameter for pagination in the request. |
|
|
|
Please provide a valid sort by field when using the 'sortBy' parameter for pagination in the request. |
|
|
|
The maximum number of buckets has already been reached. Unable to create a new bucket. |
|
|
|
The bucket name provided already exists. Please choose a different name for the bucket. |
|
|
|
The requested bucket size exceeds the maximum allowed size. Please choose a smaller size for the bucket. |
|
|
|
The requested bucket size exceeds the maximum allowed size. Please choose a smaller size for the bucket. |
|
|
|
When creating a bucket with the Magma storage engine, please ensure that the Couchbase Server version is at least 7.1. |
|
|
|
The provided durability level is not supported. The supported levels are 'none', 'majority', 'persistToMajority', and 'majorityAndPersistActive'. Please choose a valid durability level for the bucket. |
|
|
|
The requested number of replicas exceeds the maximum allowed replicas based on the cluster configuration. Please reduce the number of replicas for the bucket. |
|
|
|
The associated cluster for the bucket could not be located. Please ensure that the cluster exists and try again. |
|
|
|
The requested action or configuration change is not supported for the cluster's architecture. Please ensure the cluster has a supported architecture. |
|
|
|
The architecture of the cluster could not be determined. |
|
|
|
Memory Only (ephemeral) buckets are not currently enabled. |
|
|
|
The bucket name is not valid. A bucket name cannot be empty. Please provide a valid name for the bucket. |
|
|
|
The bucket name provided is not valid. A bucket name cannot start with a dot ('.'). Please provide a valid name for the bucket. |
|
|
|
The bucket name provided is not valid. The maximum length of the bucket name can be 100 characters. Please provide a valid name for the bucket within the allowed length. |
|
|
|
The bucket name contains an invalid character. Supported characters are those in the ranges of A-Z, a-z, and 0-9; plus the underscore, period, dash, and percent characters. Please provide a valid name for the bucket. |
|
|
|
Bucket type is required when creating a bucket, and must be one of 'couchbase' or 'ephemeral'. Please specify a valid bucket type for the bucket. |
|
|
|
The provided bucket type is invalid. Bucket type must be one of 'couchbase' or 'ephemeral'. Please provide a valid bucket type for the bucket. |
|
|
|
storageBackend is an invalid configuration option for Memory Only buckets. Either switch to a Memory and Disk bucket or remove the 'storageBackend' payload from the request. |
|
|
|
evictionPolicy is required for Memory Only buckets and must be one of 'nruEviction' or 'noEviction'. Please specify a valid eviction policy for the Memory Only bucket. |
|
|
|
The provided evictionPolicy is invalid for Memory Only buckets. evictionPolicy must be one of 'noEviction' or 'nruEviction'. Please provide a valid eviction policy for the Memory Only bucket. |
|
|
|
The provided durabilityLevel is invalid for Memory Only buckets. Valid options are none and majority. Please provide a valid durability level for the Memory Only bucket. |
|
|
|
The provided evictionPolicy is an invalid configuration option for Couchbase (Memory and Disk) buckets. Please specify 'fullEviction', or remove the evictionPolicy payload from the request to use the default ('fullEviction'). |
|
|
|
Cannot create Magma bucket. The requested size of the Magma bucket is less than the minimum amount of 1024MB. Please choose a larger size for the Magma bucket. |
|
|
|
Cannot create bucket. The requested size of the bucket is less than the minimum amount of 100MB. Please choose a larger size for the bucket. |
|
|
|
The replica count provided for the bucket is not valid. The maximum number of replicas is 3. Please reduce the number of replicas for the bucket. |
|
|
|
The TTL given is too large. The maximum allowed TTL is 2147483647 seconds. Please choose a smaller TTL for the bucket. |
|
|
|
The replica count provided for the bucket is not valid. The minimum number of replicas is 1. Please increase the number of replicas for the bucket. |
|
|
|
Unable to migrate storage backend. The server version must be at least 7.6.0. Cannot migrate storage backend from couchstore to magma due to incorrect server version. Please make sure that the server version is >= 7.6.0. |
|
|
|
Unable to migrate bucket storage backend. The cluster is currently performing other operations. Please wait until the cluster operations succeed and then try again. Cannot migrate storage backend from couchstore to magma as the cluster is not in healthy state. Please wait until the cluster operations succeed and then try again. |
|
|
|
Returned when trying to update bucket storage backend that is already magma. Please make sure that the bucket storage backend for the buckets is couchstore in order to be migrated to magma. |
|
|
|
Cannot migrate bucket to magma as the backend storage type is not supported for migration. Please note that only couchstore buckets can be migrated to magma. |
|
|
|
Cannot modify bucket durability level as only Durability level 'none' is allowed for single node clusters. |
|
|
|
Cannot perform the action due to the entity not being in a writable state. Please wait for the entity to become writable before performing the action. |
|
|
|
Unable to process request. The backup configuration for the cluster is missing. Please submit a support request to resolve this issue. Returned when an operation against a backup config is requested and the backup config is missing. |
|
|
|
The end date of the range cannot be before the start date of the range. Returned when an end date that is before the start date of a date range is given. |
|
|
|
Unable to restore to target cluster, as it is on a different cloud provider than the source. Returned when attempting to restore from a cluster in one provider to a cluster in another. |
|
|
|
Unable to target a restore for a cluster that is not in a healthy state. Returned when attempting to create a restore job for an unhealthy cluster. |
|
|
|
Backups must be in a state of 'ready' before being used. Returned when attempting to use a backup that is not in a 'ready' state. |
|
|
|
Backup must not have expired to be used for a restore. Returned when attempting to restore a backup that has been expired. |
|
|
|
The source cluster ID is invalid. Please ensure the source cluster id matches the id in the path. Returned when attempting to restore a backup and the source cluster id does not match the cluster id in the url path of the request. |
|
|
|
Invalid restore options. Services list cannot be empty. Returned when a restore options services list is empty. |
|
|
|
Returned when a restore options services list contains an unknown service. |
|
|
|
Cycle must not have expired to be used for listing backups. Returned from API when a cycle has been found to be expired. |
|
|
|
Unable to process request for backup. Backup in pending state cannot be modified. Returned when asked to modify or delete a backup in pending state. |
|
|
|
Check email domain is valid. |
|
|
|
Email accounts using this domain is not accepted. |
|
|
|
Validation failed for the email address. |
|
|
|
Email address cannot be empty. Please provide a valid email. Ensure that you provide a non-empty email address. |
|
|
|
The provided email address email is invalid; the '@' is missing. Make sure the email address contains the '@' symbol. |
|
|
|
Ensure that the local part of the email address does not exceed 64 characters. |
|
|
|
Check that the domain part of the email address is valid. |
|
|
|
Ensure that the email address is a valid UTF-8 string. |
|
|
|
Sign in with the provided email address or use a different one. |
|
|
|
Ensure there is at least one other Organization Owner before attempting to remove this user. |
|
|
|
Role based permissions for SSO user cannot be updated when team Group Mapping is enabled. Any RBAC permission changes for an SSO user should be done through a Team except when group mapping is disabled on the Realm. |
|
|
|
Returned when attempting to create a couchstore bucket and providing an invalid storageBackend value. Use either 'couchstore' or 'magma'. |
|
|
|
The time-to-live value provided is not supported. It should be a non-negative integer. Returned when a time-to-live unit that is not supported is given during bucket creation. This should be a non-negative value. |
|
|
|
Returned when a trying to set a privilege other than data_reader / read or data_writer / write while creating a database credential. |
|
|
|
Remove this database role from every database credential that references it before deleting the role. |
|
|
|
Create the application user roles on the cluster, or remove them from the request, before assigning them to a database credential. |
|
|
|
Verify the provided appservice is in healthy state before updating. |
|
|
|
Please double-check the provided ARN and ensure it follows the correct format |
|
|
|
Please double-check the provided key name and ensure it is valid according to GCP's naming conventions. |
|
|
|
Please ensure that the configuration for the key includes metadata for either the AWS, GCP, or Azure key, and then try again. |
|
|
|
Please provide a valid tenant ID when creating a CMEK, and ensure that it is included in the request. |
|
|
|
Please ensure that the key is not in use by any nodes in your clusters before attempting to delete it. |
|
|
|
The time-to-live value provided is not supported. It should be a non-negative integer. Returned when a time-to-live unit given during collection creation is not supported. This should be a non-negative value. |
|
|
|
The scope name provided is not valid. The maximum length of the scope name can be (251) characters. Returned if when attempting to create a scope the name of the scope provided is too long. |
|
|
|
The scope name is not valid. A scope name can not be empty. Returned if when attempting to create a scope the name of the scope is empty. |
|
|
|
Returned if when attempting to create a scope the name of the scope contains an unsupported character. |
|
|
|
The scope name provided is not valid. A scope name can not start with an underscore or percentage. Returned if when attempting to create a scope the name of the scope provided starts with an underscore or percentage. |
|
|
|
Returned if when attempting to create a scope but the name of the scope already exists. |
|
|
|
The collection name provided is not valid. The maximum length of the collection name can be (251) characters. Returned if when attempting to create a collection the name of the collection provided is too long. |
|
|
|
The collection name is not valid. A collection name can not be empty. Returned if when attempting to create a collection the name of the collection is empty |
|
|
|
Returned if when attempting to create a collection the name of the collection contains an unsupported character. |
|
|
|
The collection name provided is not valid. A collection name can not start with an underscore or percentage. Returned if when attempting to create a collection the name of the collection provided starts with an underscore or percentage. |
|
|
|
Returned if when attempting to create a collection but the name of the collection already exists. |
|
|
|
Returned when the timezone in the schedule is invalid. |
|
|
|
Returned when the provided schedule is missing weekdays. |
|
|
|
Returned when the provided schedule has 'on' or 'off' day with 'on' time boundary. |
|
|
|
Returned when the provided schedule has a 'custom' day without 'from' time boundary. |
|
|
|
Returned when the provided schedule has a 'custom' day with an invalid hour value. |
|
|
|
Returned when the provided schedule has a 'custom' day with an invalid minute value. |
|
|
|
Returned when the provided schedule has a 'custom' day with 'from' boundary after 'to' boundary. |
|
|
|
Returned when the provided schedule has Custom days with an invalid state. |
|
|
|
Returned when the provided schedule has the days in an invalid order than the one specified. |
|
|
|
Returned when the provided schedule has an invalid day name. |
|
|
|
Returned when trying to create a new on/off schedule for the cluster which already exists. |
|
|
|
To change an existing Audit Log Streaming config, one must already exist. No Audit Log Streaming config currently exists. A config can be supplied using the appropriate endpoint. |
|
|
|
Log Streaming collector config not set. |
|
|
|
Invalid Generic HTTP credentials. Please provide both a username and password or neither. |
|
|
|
Date/Time format in the payload is incorrect. |
|
|
|
The request body must explicitly define whether streamingEnabled is true or false. |
|
|
|
The request body must have outputType defined. outputType must be set when either streamingEnable=true or when streamingEnabled=false and other collector config fields have been provided. |
|
|
|
The request body must have log streaming credentials defined. Credentials must be set when either streamingEnable=true or when streamingEnabled=false and other collector config fields have been provided. |
|
|
|
Returned when attempting to create or modify an app service deployment with instance desired capacity of 1, but the associated cluster is not in single node mode or the single node app service feature is not enabled for the tenant. |
|
|
|
Returned when attempting to create or modify an app service deployment with instance desired capacity of more than 1, but the associated cluster is in single node mode and the single node app service feature is enabled for the tenant. |
|
|
|
Log Streaming App Endpoint config reading and writing is only allowed while the log streaming config state is in a paused or enabled state. Try the operation again once in one of these states. |
|
|
|
Returned when the cluster rejects a collection create request because a collections limit has been reached. Delete unused collections or distribute collections across additional buckets, then try again. |
|
|
|
Returned when the TTL given during collection creation or modification is not valid. |
|
|
|
Returned when attempting to modify a collection but the server version is not supported. This operation is only supported for server version 7.6.0 and above. |
|
|
|
Returned when a time to live unit that is not supported is given during collection creation or modification. |
|
|
|
Returned when attempting to create a CMEK with an asymmetric KMS key. Please provide the ARN of a symmetric KMS key. |
|
|
|
Adding a third party alert notification requires a paid plan. Upgrade to a Capella paid plan to configure an alert integration Returned when a trial account user tries to use the Alert Integration feature. |
|
|
|
Please ensure cloud provider provided is valid. |
|
|
|
Please enter the valid region for cluster deployment |
|
|
|
Please ensure couchbase server requested for cluster deployment is supported. |
|
|
|
Please ensure availability zones count is sufficient for selected cluster configuration type. |
|
|
|
Please ensure cluster configuration provided ensures specifying availability zones. |
|
|
|
Please ensure availability zones specified is valid. |
|
|
|
Please ensure selected support plan supports specifying availability zones configuration. |
|
|
|
Please ensure selected support plan supports specifying availability zones configuration. |
|
|
|
Please ensure any service is not repeated in more than one service group. |
|
|
|
Please ensure node count is 1 for single node cluster deployments. |
|
|
|
Please ensure node count for service group containing data service is between (3) and (27). |
|
|
|
Please ensure all service groups have node count more then the allowed minimum. Additional service groups can have 2 nodes minimum and 24 nodes maximum. |
|
|
|
Please ensure that number of nodes for deployment request is between (3) and (27). |
|
|
|
Please ensure data service is present in at least one of the service groups while deploying cluster. |
|
|
|
Please ensure that the current compute type can be modified to the one provided. |
|
|
|
Please ensure that the type, the size, and the IOPS (if applicable) of a disk are not modified. |
|
|
|
Please ensure that the modified number of nodes is between (3) and (27). |
|
|
|
Please ensure the IOPS value is in the correct range for the selected Ultra disk size. |
|
|
|
Cannot set replica count other than '0' for single-node clusters. |
|
|
|
Returned when attempting to create a new VPC peering relationship but the cloud service provider provided is not valid. |
|
|
|
Returned when trying to retrieve command when the admin consent has not been granted by the customer or the consent granted by the customer has not been successfully verified. |
|
|
|
Cannot delete cluster when deletion protection is enabled. |
|
|
|
Cannot delete app service when deletion protection is enabled on linked cluster. |
|
|
|
The description provided is too long. The maximum length of the description can be 256 characters. |
|
|
|
The 'scope' field contains an empty value after the leading and trailing whitespace has been trimmed. Please remove this value and resubmit the request. |
|
|
|
Cluster state is not valid for express scaling. |
|
|
|
The given score threshold is invalid. Returned when asked to use semantic cache with an invalid score threshold. |
|
|
|
The given compute configuration is invalid. Returned when asked to use an invalid compute configuration. |
|
|
|
The given compute size category is invalid. Returned when asked to use an invalid compute size category. |
|
|
|
The given compute count is invalid. Returned when asked to use an invalid compute count. |
|
|
|
Cannot list models in the given region as it is not supported. Returned when asked to list language models in an invalid aws region. |
|
|
|
The given cluster configuration is ineligible for deploying a language model. The cluster should not have a single Availability Zone in the region. Returned when asked to deploy a language model in a single Availability Zone cluster configuration. |
|
|
|
Returned when attempting to list language models having a specified deployment status. |
|
|
|
Returned when asked to deploy a language model without a specified region. |
|
|
|
Returned when asked to deploy a language model without a specified provider. |
|
|
|
Unable to deploy Language Model. 'Search' service is required to deploy a Language model. Returned when user tries to deploy a language model but 'Search' service is missing. |
|
|
|
Returned when user tries to enable security configuration (guardrails or jailbreak) for a model in a tenant where no security models are already deployed |
|
|
|
Name is required Returned when attempting to create a integration, but the name is empty |
|
|
|
Key is required Returned when attempting to create a integration, but the key is empty |
|
|
|
Returned when attempting to create an integration with already existing integration name |
|
|
|
Returned when attempting to process a request with unsupported integration |
|
|
|
Returned when attempting to process a request with unsupported integration |
|
|
|
Returned when attempting to process a request with unsupported integration |
|
|
|
Returned when attempting to create a integration with invalid s3 payload |
|
|
|
Returned when attempting to create a integration with invalid openAI payload |
|
|
|
Returned when attempting to create a integration with invalid bedrock payload |
|
|
|
The integration name provided is not valid. The integration name should not be empty, missing or consist only of whitespace. Returned when attempting to create a integration with invalid integration Name. |
|
|
|
The integration name provided is not valid. The integration name should not be greater than 50 characters. Returned when attempting to create a integration with invalid integration Name. |
|
|
|
The integration name provided is not valid. The integration name should be alphanumeric. Returned when attempting to create a integration with invalid integration Name. |
|
|
|
Returned when user tries to deploy a model but has already deployed the maximum allowed in the tenant. |
|
|
|
Returned when attempting to deploy a language model but the provider is not supported. |
|
|
|
Returned when attempting to deploy a language model but the region is not supported. |
|
|
|
Returned when attempting to process a request with invalid provider payload |
|
|
|
Returned when an invalid IP is provided for the APIKey. |
|
|
|
APIKey expiry duration is invalid Returned when an invalid expiry duration is provided for the APIKey. The expiry duration must be less than or equal to 365 days. |
|
|
|
Private Endpoint Provider is already enabled for this region and provider. Returned when attempting to enable private endpoint provider for the region and provider that already has them enabled. |
|
|
|
Private Endpoint Provider is not enabled for this region and provider. Returned when attempting to disable private endpoint provider for the region and provider and private endpoint provider is not enabled. |
|
|
|
Endpoint provider not found. Returned when id is provided that doesn't exists. |
|
|
|
Returned when attempting to enable private endpoints for a provider that is not supported. |
|
|
|
Cluster ID cannot be empty. Returned when attempting to add interface endpoint without providing a cluster ID. |
|
|
|
Returned when attempting to perform an invalid action on a model. |
|
|
|
Model endpoint provider ID cannot be empty. Returned when endpoint provider ID is not provided for any endpoint operations. |
|
|
|
VPC ID cannot be empty. Returned when attempting to add interface endpoint without providing a VPC ID. |
|
|
|
Subnet IDs cannot be empty. Returned when attempting to add interface endpoint without providing subnet IDs. |
|
|
|
Service Source is missing. Returned while attempting to add an entry to the allowlist; however, the initiating service is missing |
|
|
|
AWS Bedrock API key integration is disabled for your organization. Please speak to Capella support for more information. Returned when attempting to create or update an AWS Bedrock integration that uses API-key authentication (or to reference one from an AI workflow) while the bedrock-api-key-integration feature flag is disabled for the tenant. IAM-credential Bedrock integrations are not gated. |
|
|
|
Private networking for AWS Bedrock workflows is disabled for your organization. Please speak to Capella support for more information. Returned when creating an AI workflow that sets privateEndpointEnabled on its external AWS Bedrock embedding model while the bedrock-private-endpoint feature flag is disabled for the tenant. |
|
|
|
The integration's region cannot be changed while AI workflows with private networking are using it. Delete those workflows first, then update the region. Returned when attempting to change the region of an AWS Bedrock integration that is referenced by AI workflows with privateEndpointEnabled. The private endpoint is provisioned for the integration's region; changing the region would orphan it. Other integration fields, such as rotated credentials, remain updatable. |
|
|
|
The integration cannot be deleted while AI workflows with private networking are using it. Delete those workflows first, then delete the integration. Returned when attempting to delete an AWS Bedrock integration that is referenced by AI workflows with privateEndpointEnabled. The workflow destroy path resolves the Bedrock region from the integration to tear down the shared private endpoint, so deleting the integration first would leave the workflows undestroyable and the endpoint orphaned. |
|
|
|
The backup exceeds the 5 TB maximum size supported for export. Returned when attempting to export a backup larger than the 5 TB export size limit. Exports of larger backups are not supported; restore the backup to a cluster instead. |
|
|
|
The provided agent memory server configuration is invalid. Returned when the agent memory server configuration fails validation. Verify that all required configuration fields are present and valid, for example that the model is offered by the specified integration and that limits are within the allowed range. |
|
|
|
Returned when the agent memory server request is well-formed but semantically invalid. Check that the target cluster is healthy and meets all prerequisites for the operation. |
|
|
|
The cluster is not eligible for an agent memory server deployment. The cluster must run the data, index, query, and search services and be on Couchbase Server 8.0.0 or later. Returned when the target cluster does not meet the service or version requirements for an agent memory server deployment. Ensure the cluster has the data, index, query, and search services enabled and is running Couchbase Server version 8.0.0 or later. |
|
|
|
The provided access policy is invalid. Returned when the access policy for an agent memory server API key uses unsupported roles. Check the API documentation for the list of valid access policy roles. |
|
|
|
Returned when the supplied allowed CIDR does not parse as a valid CIDR block. Ensure the value is a valid IPv4 CIDR (e.g. 10.0.0.0/24). |
|
|
|
Returned when the supplied allowed CIDR is IPv6. The agent memory server load balancer is IPv4-only; provide an IPv4 CIDR block instead. |
|
|
|
Returned when the supplied allowed CIDR has host bits set. Use the network address form of the CIDR (e.g. use 10.1.0.0/16 instead of 10.1.2.3/16). |
|
|
|
Returned when adding a CIDR would take the agent memory server allowlist past its maximum number of entries. Remove unused CIDR entries before adding new ones. |
|
HTTP Status 429
Too many requests.
| Code | Name | Description | HTTP Status |
|---|---|---|---|
|
|
Oops! You've made too many requests. Please wait for time specified in the retryAfter header before trying again. The number of requests allowed per API key has exceeded. Please retry after time specified in the retryAfter header has passed. |
|
HTTP Status 500
Internal server errors.
| Code | Name | Description | HTTP Status |
|---|---|---|---|
|
|
An internal server error occurred. Something went wrong on our end. We are actively investigating the issue. |
|
|
|
An internal server error occurred. Something went wrong on our end. We are actively investigating the issue. |
|
|
|
An internal server error occurred. Something went wrong on our end. We are actively investigating the issue. |
|
|
|
An internal server error occurred. Something went wrong on our end. We are actively investigating the issue. |
|
|
|
An internal server error occurred. Something went wrong on our end. We are actively investigating the issue. |
|
|
|
An internal server error occurred. Something went wrong on our end. We are actively investigating the issue. |
|
|
|
An internal server error occurred. Something went wrong on our end. We are actively investigating the issue. |
|
Agent Memory API Error Messages
HTTP Status 400
Bad request.
| Code | Name | Description | HTTP Status |
|---|---|---|---|
|
|
Session has already ended The session has already been ended and cannot be ended again or written to. Start a new session for further activity. |
|
|
|
A prompt reference was provided but semantic extraction is disabled for this call A prompt_id was supplied while semantic extraction was turned off for the request. Enable extraction, or drop the prompt reference. |
|
|
|
Invalid request The request was rejected as malformed — for example an unparseable filter or other caller-supplied value. Correct the request and resend. |
|
HTTP Status 401
Unauthorized.
| Code | Name | Description | HTTP Status |
|---|---|---|---|
|
|
Invalid token The bearer token is malformed, has invalid claims, or is an ID token rather than an access token. Send a valid OIDC access token in the Authorization header. |
|
|
|
Token has expired The access token is past its expiry. Obtain a fresh token from your identity provider and retry. |
|
|
|
Token validation failed The token could not be validated against the identity provider's keys. Confirm the token was issued by the configured issuer and audience, then retry with a new token. |
|
|
|
Authentication required No bearer token was supplied for a protected route. Include an Authorization=Bearer <access_token> header. |
|
HTTP Status 403
Forbidden.
| Code | Name | Description | HTTP Status |
|---|---|---|---|
|
|
Insufficient permissions The token is valid but carries no AMS role, or a role below the tier this route requires (ams_ro < ams_rw < ams_admin). The response names the required tier. Grant the caller the needed role. |
|
HTTP Status 404
Not found.
| Code | Name | Description | HTTP Status |
|---|---|---|---|
|
|
User not found No user exists for the user_id in the path. Create the user first, or check the identifier. |
|
|
|
Session not found No session exists for the given session_id (and user_id, when the lookup is user-scoped). Create the session first, or check the identifiers. |
|
|
|
Prompt not found No prompt exists for the given prompt_id. Register the prompt first, or check the identifier. |
|
|
|
Prompt version not found The requested version of the prompt does not exist. List the prompt's versions and reference an existing one. |
|
|
|
Memory block not found No memory block exists for the given id (within the session, when the lookup is session-scoped). Check the block id, or note that only READY blocks are retrievable. |
|
|
|
Resource not found No route matches the requested method and path. Check the URL and HTTP method against the API reference. |
|
HTTP Status 409
Conflict.
| Code | Name | Description | HTTP Status |
|---|---|---|---|
|
|
User already exists A user with this user_id already exists. Use a different id, or fetch/update the existing user instead of creating it. |
|
|
|
Session already exists A session with this session_id already exists for the user. Use a different id, or continue with the existing session. |
|
|
|
Prompt already exists A prompt with this prompt_id already exists. Use a different id, or update the existing prompt to create a new version. |
|
|
|
Prompt has been archived and can no longer be referenced or re-created The whole prompt id has been archived. Reference a different prompt; an archived id cannot be reused or recreated. |
|
|
|
Prompt has already been archived The prompt is already archived, so it cannot be archived again. No action needed. |
|
|
|
Prompt version has been archived and can no longer be pinned to The referenced prompt version is archived and cannot be pinned to. Pin to a live version instead. |
|
|
|
Prompt version has already been archived The prompt version is already archived, so it cannot be archived again. No action needed. |
|
|
|
Cannot purge the current version of a prompt — update it to a new version first, or purge the whole prompt instead Purging the version currently in use is not allowed. Update the prompt to a new current version first, then purge the old one, or purge the entire prompt. |
|
|
|
Cannot archive the current version of a prompt — update it to a new version first, or archive the whole prompt instead Archiving the version currently in use is not allowed. Update the prompt to a new current version first, then archive the old one, or archive the entire prompt. |
|
|
|
Prompt is currently being purged A purge of this prompt is already in progress. Wait for it to finish before issuing another purge. |
|
|
|
Memory block is currently being processed The block is mid semantic-extraction and cannot be updated right now. This is transient; retry after the interval in the Retry-After header. |
|
HTTP Status 422
Unprocessable content.
| Code | Name | Description | HTTP Status |
|---|---|---|---|
|
|
Request validation failed The request body or parameters failed schema validation. details.fields lists each offending field and why. Fix those fields and resend. |
|
HTTP Status 429
Too many requests.
| Code | Name | Description | HTTP Status |
|---|---|---|---|
|
|
Memory processing queue is full The asynchronous extraction queue is at capacity, so the block was not accepted. Back off and retry after the Retry-After header; details.queue_size and details.queue_max_size report current depth. |
|
HTTP Status 500
Internal server errors.
| Code | Name | Description | HTTP Status |
|---|---|---|---|
|
|
User operation failed An unexpected server-side error occurred while processing the user operation. Retry; if it persists, contact support with the request_id. |
|
|
|
Session operation failed An unexpected server-side error occurred while processing the session operation. Retry; if it persists, contact support with the request_id. |
|
|
|
Prompt operation failed An unexpected server-side error occurred while processing the prompt operation. Retry; if it persists, contact support with the request_id. |
|
|
|
Failed to delete memory block The block could not be deleted due to a server-side error. Retry; if it persists, contact support with the request_id. |
|
|
|
Failed to generate embeddings for memory blocks The embedding provider returned an error while embedding the submitted blocks. Retry; if it persists, check the embedding model configuration and provider status. |
|
|
|
Memory block operation failed An unexpected server-side error occurred while processing the memory block. Retry; if it persists, contact support with the request_id. |
|
|
|
Database operation failed A non-transient Couchbase failure that will not improve on retry. When a bucket, scope, collection, keyspace, or index is missing, details.service, details.resource, and details.name identify it; other database faults (e.g. a malformed query) carry no details and only a request_id. Check that the configured storage and FTS indexes exist. |
|
|
|
Internal server error An unhandled server-side error occurred. Retry; if it persists, contact support with the request_id from the response. |
|
HTTP Status 502
Bad gateway.
| Code | Name | Description | HTTP Status |
|---|---|---|---|
|
|
Unable to connect to model service The server could not open a connection to the model provider. The body message is generic by design; the failure is identified by the X-Upstream-Service and X-Error-Class=connection_error response headers, and the underlying error is logged against the request_id. Check network egress to the provider and provider status, then retry. |
|
|
|
Model service error The model provider returned an unexpected error. The body message is generic; X-Upstream-Service and X-Error-Class (the provider error class) name the failure, and the detail is logged against the request_id. Retry; if it persists, check provider status. |
|
HTTP Status 503
Service unavailable.
| Code | Name | Description | HTTP Status |
|---|---|---|---|
|
|
Authentication service temporarily unavailable The identity provider (OIDC discovery or JWKS endpoint) is unreachable, so the token could not be validated. This is transient and unrelated to the token itself; retry after a short delay. |
|
|
|
Database is temporarily unavailable A transient Couchbase failure (timeout or connection loss) occurred. This is retryable; retry after a short delay. details.service is "database". |
|
|
|
Embedding service is unavailable The embedding model failed its health check and requests are being blocked. details.service is "embedding". Retryable once the provider recovers; check the embedding model configuration and provider status. |
|
|
|
LLM service is unavailable The LLM (extraction) model failed its health check and requests are being blocked. details.service is "llm". Retryable once the provider recovers; check the LLM model configuration and provider status. |
|
|
|
Model service authentication failed The model provider rejected the configured API key. Identified by the X-Upstream-Service and X-Error-Class=authentication_error response headers. This is a server configuration issue, not the caller's; rotate or correct the provider API key. |
|
|
|
Model health check failed A pre-request model health check failed. The X-Upstream-Service=model response header marks it; no details object is returned. Retryable once the model recovers; check the model configuration and provider status. |
|
|
|
Model service temporarily unavailable due to upstream rate limiting The model provider rate-limited this deployment and internal retries were exhausted. details.retry_after_seconds and details.service (embedding/llm/unknown) accompany it, mirrored by the Retry-After and X-Error-Class=rate_limit_exhausted headers. Back off and retry after Retry-After. |
|
|
|
Model provider account quota exhausted — retrying will not help The model provider account is out of quota or credits. details.service names the affected model and details.retry_after_seconds is 0; the X-Error-Class=quota_exhausted header marks it and no Retry-After is sent. This is permanent until resolved; top up credits or rotate the API key. |
|
|
|
Server is under memory pressure The server is shedding load because memory usage crossed its threshold. No details object is returned; the Retry-After and X-Memory-Usage-Percent response headers carry the specifics. Back off and retry after Retry-After. |
|
HTTP Status 504
Gateway timeout.
| Code | Name | Description | HTTP Status |
|---|---|---|---|
|
|
Model service request timed out The model provider did not respond within the timeout. Identified by the X-Upstream-Service and X-Error-Class=timeout response headers. Retry; if it persists, check provider status and latency. |
|
See Also
-
For details of the Management API and the Agent Memory API, see Agent Memory APIs for Managed Deployments.
-
For a full reference guide to the Management API, see Couchbase Capella Management API Reference.
-
For a full reference guide to the Agent Memory API, see Agent Memory API Reference.