ArangoDB v3.12 is under development and not released yet. This documentation is not final and potentially incomplete.

Error codes and meanings

An error reply from ArangoDB servers contain a code, error number, and message and you can look up additional information for a specific kind of error

Numbers, names, and descriptions of errors

When an error occurs in an operation of an ArangoDB server, the HTTP REST API responds to a request with an HTTP status code like 400 Bad Request, 401 Unauthorized, 503 Service Unavailable, or similar. This code is typically also included in the body of the response, specifically the code attribute, along with the error attribute set to true.

HTTP/1.1 401 Unauthorized
...

{"code":401,"error":true,"errorNum":11,"errorMessage":"not authorized to execute this request"}

The error code only indicates the broad category of an error, based on the status codes defined by the HTTP protocol.

A more detailed error number is provided in the errorNum attribute. Error numbers are specific to ArangoDB. Each ArangoDB error kind has a number, a unique name, an error message, and a description.

The error message is a brief description of the error and provided in the errorMessage attribute.

Error names are used in code to refer to an error kind, in the server’s own code as well as in other code like drivers. For instance, the name for the error with the number 11 is ERROR_FORBIDDEN. The error name is not visible in the HTTP API response.

In the JavaScript API, the @arangodb module maps error names to objects with the error number and message:

require("@arangodb").errors.ERROR_FORBIDDEN
{
  "code" : 11,
  "message" : "forbidden"
}

Note that the error message in the HTTP API response deviates from the above shown message (“not authorized to execute this request” versus “forbidden”). ArangoDB does not necessarily return the error message as defined internally but can override it in order to provide more details. You should therefore check against the error number in your own code and never rely on the error message, as it can be different in under different circumstances for the same error kind.

An error description is a more detailed description of the error kind than the error message. It is not visible in the HTTP API response. It is mainly used to provide context for developers.

List of error codes

In the following, you find the error kinds that exist in ArangoDB, grouped into categories. The format is number - message for headlines and the error descriptions as the text.

General errors

0 - ERROR_NO_ERROR

No error has occurred.

1 - ERROR_FAILED

Will be raised when a general error occurred.

2 - ERROR_SYS_ERROR

Will be raised when operating system error occurred.

3 - ERROR_OUT_OF_MEMORY

Will be raised when there is a memory shortage.

4 - ERROR_INTERNAL

Will be raised when an internal error occurred.

5 - ERROR_ILLEGAL_NUMBER

Will be raised when an illegal representation of a number was given.

6 - ERROR_NUMERIC_OVERFLOW

Will be raised when a numeric overflow occurred.

7 - ERROR_ILLEGAL_OPTION

Will be raised when an unknown option was supplied by the user.

8 - ERROR_DEAD_PID

Will be raised when a PID without a living process was found.

9 - ERROR_NOT_IMPLEMENTED

Will be raised when hitting an unimplemented feature.

10 - ERROR_BAD_PARAMETER

Will be raised when the parameter does not fulfill the requirements.

11 - ERROR_FORBIDDEN

Will be raised when you are missing permission for the operation.

12 - ERROR_OUT_OF_MEMORY_MMAP

Will be raised when there is a memory shortage.

13 - ERROR_CORRUPTED_CSV

Will be raised when encountering a corrupt csv line.

14 - ERROR_FILE_NOT_FOUND

Will be raised when a file is not found.

15 - ERROR_CANNOT_WRITE_FILE

Will be raised when a file cannot be written.

16 - ERROR_CANNOT_OVERWRITE_FILE

Will be raised when an attempt is made to overwrite an existing file.

17 - ERROR_TYPE_ERROR

Will be raised when a type error is encountered.

18 - ERROR_LOCK_TIMEOUT

Will be raised when there's a timeout waiting for a lock.

19 - ERROR_CANNOT_CREATE_DIRECTORY

Will be raised when an attempt to create a directory fails.

20 - ERROR_CANNOT_CREATE_TEMP_FILE

Will be raised when an attempt to create a temporary file fails.

21 - ERROR_REQUEST_CANCELED

Will be raised when a request is canceled by the user.

22 - ERROR_DEBUG

Will be raised intentionally during debugging.

25 - ERROR_IP_ADDRESS_INVALID

Will be raised when the structure of an IP address is invalid.

27 - ERROR_FILE_EXISTS

Will be raised when a file already exists.

28 - ERROR_LOCKED

Will be raised when a resource or an operation is locked.

29 - ERROR_DEADLOCK

Will be raised when a deadlock is detected when accessing collections.

30 - ERROR_SHUTTING_DOWN

Will be raised when a call cannot succeed because a server shutdown is already in progress.

31 - ERROR_ONLY_ENTERPRISE

Will be raised when an Enterprise Edition feature is requested from the Community Edition.

32 - ERROR_RESOURCE_LIMIT

Will be raised when the resources used by an operation exceed the configured maximum value.

33 - ERROR_ARANGO_ICU_ERROR

will be raised if ICU operations failed.

34 - ERROR_CANNOT_READ_FILE

Will be raised when a file cannot be read.

35 - ERROR_INCOMPATIBLE_VERSION

Will be raised when a server is running an incompatible version of ArangoDB.

36 - ERROR_DISABLED

Will be raised when a requested resource is not enabled.

37 - ERROR_MALFORMED_JSON

Will be raised when a JSON string could not be parsed.

38 - ERROR_STARTING_UP

Will be raised when a call cannot succeed because the server startup phase is still in progress.

39 - ERROR_DESERIALIZE

Will be raised when a data structure cannot be deserialized, e.g. because the input is invalid.

40 - ERROR_END_OF_FILE

Will be raised when a read operation reaches the end of the file.

HTTP error status codes

400 - ERROR_HTTP_BAD_PARAMETER

Will be raised when the HTTP request does not fulfill the requirements.

401 - ERROR_HTTP_UNAUTHORIZED

Will be raised when authorization is required but the user is not authorized.

403 - ERROR_HTTP_FORBIDDEN

Will be raised when the operation is forbidden.

404 - ERROR_HTTP_NOT_FOUND

Will be raised when an URI is unknown.

405 - ERROR_HTTP_METHOD_NOT_ALLOWED

Will be raised when an unsupported HTTP method is used for an operation.

406 - ERROR_HTTP_NOT_ACCEPTABLE

Will be raised when an unsupported HTTP content type is used for an operation, or if a request is not acceptable for a leader or follower.

408 - ERROR_HTTP_REQUEST_TIMEOUT

Will be raised when a timeout occured.

409 - ERROR_HTTP_CONFLICT

Will be raised when a conflict occurs in an HTTP operation.

410 - ERROR_HTTP_GONE

Will be raised when the requested content has been permanently deleted.

412 - ERROR_HTTP_PRECONDITION_FAILED

Will be raised when a precondition for an HTTP request is not met.

420 - ERROR_HTTP_ENHANCE_YOUR_CALM

Will be raised when too many requests were sent to a rate-limited API.

500 - ERROR_HTTP_SERVER_ERROR

Will be raised when an internal server is encountered.

501 - ERROR_HTTP_NOT_IMPLEMENTED

Will be raised when an API is called this is not implemented in general, or not implemented for the current setup.

503 - ERROR_HTTP_SERVICE_UNAVAILABLE

Will be raised when a service is temporarily unavailable.

504 - ERROR_HTTP_GATEWAY_TIMEOUT

Will be raised when a service contacted by ArangoDB does not respond in a timely manner.

HTTP processing errors

600 - ERROR_HTTP_CORRUPTED_JSON

Will be raised when a string representation of a JSON object is corrupt.

601 - ERROR_HTTP_SUPERFLUOUS_SUFFICES

Will be raised when the URL contains superfluous suffices.

Internal ArangoDB storage errors

1000 - ERROR_ARANGO_ILLEGAL_STATE

Internal error that will be raised when the datafile is not in the required state.

1004 - ERROR_ARANGO_READ_ONLY

Internal error that will be raised when trying to write to a read-only datafile or collection.

1005 - ERROR_ARANGO_DUPLICATE_IDENTIFIER

Internal error that will be raised when a identifier duplicate is detected.

External ArangoDB storage errors

1100 - ERROR_ARANGO_CORRUPTED_DATAFILE

Will be raised when a corruption is detected in a datafile.

1101 - ERROR_ARANGO_ILLEGAL_PARAMETER_FILE

Will be raised if a parameter file is corrupted or cannot be read.

1102 - ERROR_ARANGO_CORRUPTED_COLLECTION

Will be raised when a collection contains one or more corrupted data files.

1104 - ERROR_ARANGO_FILESYSTEM_FULL

Will be raised when the filesystem is full.

1107 - ERROR_ARANGO_DATADIR_LOCKED

Will be raised when the database directory is locked by a different process.

General ArangoDB storage errors

1200 - ERROR_ARANGO_CONFLICT

Will be raised when updating or deleting a document and a conflict has been detected.

1202 - ERROR_ARANGO_DOCUMENT_NOT_FOUND

Will be raised when a document with a given identifier is unknown.

1203 - ERROR_ARANGO_DATA_SOURCE_NOT_FOUND

Will be raised when a collection or View with the given identifier or name is unknown.

1204 - ERROR_ARANGO_COLLECTION_PARAMETER_MISSING

Will be raised when the collection parameter is missing.

1205 - ERROR_ARANGO_DOCUMENT_HANDLE_BAD

Will be raised when a document identifier is corrupt.

1207 - ERROR_ARANGO_DUPLICATE_NAME

Will be raised when a name duplicate is detected.

1208 - ERROR_ARANGO_ILLEGAL_NAME

Will be raised when an illegal name is detected.

1209 - ERROR_ARANGO_NO_INDEX

Will be raised when no suitable index for the query is known.

1210 - ERROR_ARANGO_UNIQUE_CONSTRAINT_VIOLATED

Will be raised when there is a unique constraint violation.

1212 - ERROR_ARANGO_INDEX_NOT_FOUND

Will be raised when an index with a given identifier is unknown.

1213 - ERROR_ARANGO_CROSS_COLLECTION_REQUEST

Will be raised when a cross-collection is requested.

1214 - ERROR_ARANGO_INDEX_HANDLE_BAD

Will be raised when a index identifier is corrupt.

1216 - ERROR_ARANGO_DOCUMENT_TOO_LARGE

Will be raised when the document cannot fit into any datafile because of it is too large.

1218 - ERROR_ARANGO_COLLECTION_TYPE_INVALID

Will be raised when an invalid collection type is used in a request.

1220 - ERROR_ARANGO_ATTRIBUTE_PARSER_FAILED

Will be raised when parsing an attribute name definition failed.

1221 - ERROR_ARANGO_DOCUMENT_KEY_BAD

Will be raised when a document key is corrupt.

1222 - ERROR_ARANGO_DOCUMENT_KEY_UNEXPECTED

Will be raised when a user-defined document key is supplied for collections with auto key generation.

1224 - ERROR_ARANGO_DATADIR_NOT_WRITABLE

Will be raised when the server's database directory is not writable for the current user.

1225 - ERROR_ARANGO_OUT_OF_KEYS

Will be raised when a key generator runs out of keys.

1226 - ERROR_ARANGO_DOCUMENT_KEY_MISSING

Will be raised when a document key is missing.

1227 - ERROR_ARANGO_DOCUMENT_TYPE_INVALID

Will be raised when there is an attempt to create a document with an invalid type.

1228 - ERROR_ARANGO_DATABASE_NOT_FOUND

Will be raised when a non-existing database is accessed.

1229 - ERROR_ARANGO_DATABASE_NAME_INVALID

Will be raised when an invalid database name is used.

1230 - ERROR_ARANGO_USE_SYSTEM_DATABASE

Will be raised when an operation is requested in a database other than the system database.

1232 - ERROR_ARANGO_INVALID_KEY_GENERATOR

Will be raised when an invalid key generator description is used.

1233 - ERROR_ARANGO_INVALID_EDGE_ATTRIBUTE

will be raised when the _from or _to values of an edge are undefined or contain an invalid value.

1235 - ERROR_ARANGO_INDEX_CREATION_FAILED

Will be raised when an attempt to create an index has failed.

1237 - ERROR_ARANGO_COLLECTION_TYPE_MISMATCH

Will be raised when a collection has a different type from what has been expected.

1238 - ERROR_ARANGO_COLLECTION_NOT_LOADED

Will be raised when a collection is accessed that is not yet loaded.

1239 - ERROR_ARANGO_DOCUMENT_REV_BAD

Will be raised when a document revision is corrupt or is missing where needed.

1240 - ERROR_ARANGO_INCOMPLETE_READ

Will be raised by the storage engine when a read cannot be completed.

1241 - ERROR_ARANGO_OLD_ROCKSDB_FORMAT

Will be raised by the storage engine when an operation cannot be performed because the old, deprecated, little endian key encoding format is still used and an operation is tried which is not supported by this format.

Checked ArangoDB storage errors

1301 - ERROR_ARANGO_EMPTY_DATADIR

Will be raised when encountering an empty server database directory.

1302 - ERROR_ARANGO_TRY_AGAIN

Will be raised when an operation should be retried.

1303 - ERROR_ARANGO_BUSY

Will be raised when storage engine is busy.

1304 - ERROR_ARANGO_MERGE_IN_PROGRESS

Will be raised when storage engine has a datafile merge in progress and cannot complete the operation.

1305 - ERROR_ARANGO_IO_ERROR

Will be raised when storage engine encounters an I/O error.

ArangoDB replication errors

1400 - ERROR_REPLICATION_NO_RESPONSE

Will be raised when the replication applier does not receive any or an incomplete response from the leader.

1401 - ERROR_REPLICATION_INVALID_RESPONSE

Will be raised when the replication applier receives an invalid response from the leader.

1402 - ERROR_REPLICATION_LEADER_ERROR

Will be raised when the replication applier receives a server error from the leader.

1403 - ERROR_REPLICATION_LEADER_INCOMPATIBLE

Will be raised when the replication applier connects to a leader that has an incompatible version.

1404 - ERROR_REPLICATION_LEADER_CHANGE

Will be raised when the replication applier connects to a different leader than before.

1405 - ERROR_REPLICATION_LOOP

Will be raised when the replication applier is asked to connect to itself for replication.

1406 - ERROR_REPLICATION_UNEXPECTED_MARKER

Will be raised when an unexpected marker is found in the replication log stream.

1407 - ERROR_REPLICATION_INVALID_APPLIER_STATE

Will be raised when an invalid replication applier state file is found.

1408 - ERROR_REPLICATION_UNEXPECTED_TRANSACTION

Will be raised when an unexpected transaction id is found.

1409 - ERROR_REPLICATION_SHARD_SYNC_ATTEMPT_TIMEOUT_EXCEEDED

Will be raised when the synchronization of a shard takes longer than the configured timeout.

1410 - ERROR_REPLICATION_INVALID_APPLIER_CONFIGURATION

Will be raised when the configuration for the replication applier is invalid.

1411 - ERROR_REPLICATION_RUNNING

Will be raised when there is an attempt to perform an operation while the replication applier is running.

1412 - ERROR_REPLICATION_APPLIER_STOPPED

Special error code used to indicate the replication applier was stopped by a user.

1413 - ERROR_REPLICATION_NO_START_TICK

Will be raised when the replication applier is started without a known start tick value.

1414 - ERROR_REPLICATION_START_TICK_NOT_PRESENT

Will be raised when the replication applier fetches data using a start tick, but that start tick is not present on the logger server anymore.

1416 - ERROR_REPLICATION_WRONG_CHECKSUM

Will be raised when a new born follower submits a wrong checksum

1417 - ERROR_REPLICATION_SHARD_NONEMPTY

Will be raised when a shard is not empty and the follower tries a shortcut

1418 - ERROR_REPLICATION_REPLICATED_LOG_NOT_FOUND

Will be raised when a specific replicated log is not found

1419 - ERROR_REPLICATION_REPLICATED_LOG_NOT_THE_LEADER

Will be raised when a participant of a replicated log is ordered to do something only the leader can do

1420 - ERROR_REPLICATION_REPLICATED_LOG_NOT_A_FOLLOWER

Will be raised when a participant of a replicated log is ordered to do something only a follower can do

1421 - ERROR_REPLICATION_REPLICATED_LOG_APPEND_ENTRIES_REJECTED

Will be raised when a follower of a replicated log rejects an append entries request

1422 - ERROR_REPLICATION_REPLICATED_LOG_LEADER_RESIGNED

Will be raised when a leader instance of a replicated log rejects a request because it just resigned. This can also happen if the term changes (due to a configuration change), even if the leader stays the same.

1423 - ERROR_REPLICATION_REPLICATED_LOG_FOLLOWER_RESIGNED

Will be raised when a follower instance of a replicated log rejects a request because it just resigned. This can also happen if the term changes (due to a configuration change), even if the server stays a follower.

1424 - ERROR_REPLICATION_REPLICATED_LOG_PARTICIPANT_GONE

Will be raised when a participant instance of a replicated log is no longer available.

1425 - ERROR_REPLICATION_REPLICATED_LOG_INVALID_TERM

Will be raised when a participant tries to change its term but found a invalid new term.

1426 - ERROR_REPLICATION_REPLICATED_LOG_UNCONFIGURED

Will be raised when a participant is currently unconfigured, i.e. neither a leader nor a follower.

1427 - ERROR_REPLICATION_REPLICATED_STATE_NOT_FOUND

Will be raised when a specific replicated state was not found.

1428 - ERROR_REPLICATION_REPLICATED_STATE_NOT_AVAILABLE

Will be raised when a specific replicated state was accessed but is not (yet) available.

1429 - ERROR_REPLICATION_WRITE_CONCERN_NOT_FULFILLED

Will be raised when there are not enough replicas of a shard available to fulfill the write-concern for a write operation.

1430 - ERROR_REPLICATION_REPLICATED_LOG_SUBSEQUENT_FAULT

Will be raised when an operation is aborted due to a cascading failure.

1431 - ERROR_REPLICATION_REPLICATED_STATE_IMPLEMENTATION_NOT_FOUND

Will be raised when a specific replicated state type was used but is not (yet) available.

1432 - ERROR_REPLICATION_REPLICATED_WAL_ERROR

Will be raised when an error occurred in the replicated WAL subsystem

1433 - ERROR_REPLICATION_REPLICATED_WAL_INVALID_FILE

Will be raised when a log file has an invalid or missing file header.

1434 - ERROR_REPLICATION_REPLICATED_WAL_CORRUPT

Will be raised when a log file has an invalid size or reading from a log file produced unexpected data.

ArangoDB cluster errors

1446 - ERROR_CLUSTER_NOT_FOLLOWER

Will be raised when an operation is sent to a non-following server.

1447 - ERROR_CLUSTER_FOLLOWER_TRANSACTION_COMMIT_PERFORMED

Will be raised when a follower transaction has already performed an intermediate commit and must be rolled back.

1448 - ERROR_CLUSTER_CREATE_COLLECTION_PRECONDITION_FAILED

Will be raised when updating the plan on collection creation failed.

1449 - ERROR_CLUSTER_SERVER_UNKNOWN

Will be raised on some occasions when one server gets a request from another, which has not (yet?) been made known via the Agency.

1450 - ERROR_CLUSTER_TOO_MANY_SHARDS

Will be raised when the number of shards for a collection is higher than allowed.

1454 - ERROR_CLUSTER_COULD_NOT_CREATE_COLLECTION_IN_PLAN

Will be raised when a Coordinator in a cluster cannot create an entry for a new collection in the Plan hierarchy in the Agency.

1456 - ERROR_CLUSTER_COULD_NOT_CREATE_COLLECTION

Will be raised when a Coordinator in a cluster notices that some DB-Servers report problems when creating shards for a new collection.

1457 - ERROR_CLUSTER_TIMEOUT

Will be raised when a Coordinator in a cluster runs into a timeout for some cluster wide operation.

1458 - ERROR_CLUSTER_COULD_NOT_REMOVE_COLLECTION_IN_PLAN

Will be raised when a Coordinator in a cluster cannot remove an entry for a collection in the Plan hierarchy in the Agency.

1460 - ERROR_CLUSTER_COULD_NOT_CREATE_DATABASE_IN_PLAN

Will be raised when a Coordinator in a cluster cannot create an entry for a new database in the Plan hierarchy in the Agency.

1461 - ERROR_CLUSTER_COULD_NOT_CREATE_DATABASE

Will be raised when a Coordinator in a cluster notices that some DB-Servers report problems when creating databases for a new cluster wide database.

1462 - ERROR_CLUSTER_COULD_NOT_REMOVE_DATABASE_IN_PLAN

Will be raised when a Coordinator in a cluster cannot remove an entry for a database in the Plan hierarchy in the Agency.

1463 - ERROR_CLUSTER_COULD_NOT_REMOVE_DATABASE_IN_CURRENT

Will be raised when a Coordinator in a cluster cannot remove an entry for a database in the Current hierarchy in the Agency.

1464 - ERROR_CLUSTER_SHARD_GONE

Will be raised when a Coordinator in a cluster cannot determine the shard that is responsible for a given document.

1465 - ERROR_CLUSTER_CONNECTION_LOST

Will be raised when a Coordinator in a cluster loses an HTTP connection to a DB-Server in the cluster whilst transferring data.

1466 - ERROR_CLUSTER_MUST_NOT_SPECIFY_KEY

Will be raised when a Coordinator in a cluster finds that the _key attribute was specified in a sharded collection the uses not only _key as sharding attribute.

1467 - ERROR_CLUSTER_GOT_CONTRADICTING_ANSWERS

Will be raised if a Coordinator in a cluster gets conflicting results from different shards, which should never happen.

1468 - ERROR_CLUSTER_NOT_ALL_SHARDING_ATTRIBUTES_GIVEN

Will be raised if a Coordinator tries to find out which shard is responsible for a partial document, but cannot do this because not all sharding attributes are specified.

1469 - ERROR_CLUSTER_MUST_NOT_CHANGE_SHARDING_ATTRIBUTES

Will be raised if there is an attempt to update the value of a shard attribute.

1470 - ERROR_CLUSTER_UNSUPPORTED

Will be raised when there is an attempt to carry out an operation that is not supported in the context of a sharded collection.

1471 - ERROR_CLUSTER_ONLY_ON_COORDINATOR

Will be raised if there is an attempt to run a Coordinator-only operation on a different type of node.

1472 - ERROR_CLUSTER_READING_PLAN_AGENCY

Will be raised if a Coordinator or DB-Server cannot read the Plan in the Agency.

1474 - ERROR_CLUSTER_AQL_COMMUNICATION

Will be raised if the internal communication of the cluster for AQL produces an error.

1477 - ERROR_CLUSTER_ONLY_ON_DBSERVER

Will be raised if there is an attempt to run a DB-Server-only operation on a different type of node.

1478 - ERROR_CLUSTER_BACKEND_UNAVAILABLE

Will be raised if a required DB-Server can't be reached.

1481 - ERROR_CLUSTER_AQL_COLLECTION_OUT_OF_SYNC

Will be raised if a collection/view needed during query execution is out of sync. This currently can happen when using SatelliteCollections, Arangosearch links or inverted indexes.

1482 - ERROR_CLUSTER_COULD_NOT_CREATE_INDEX_IN_PLAN

Will be raised when a Coordinator in a cluster cannot create an entry for a new index in the Plan hierarchy in the Agency.

1483 - ERROR_CLUSTER_COULD_NOT_DROP_INDEX_IN_PLAN

Will be raised when a Coordinator in a cluster cannot remove an index from the Plan hierarchy in the Agency.

1484 - ERROR_CLUSTER_CHAIN_OF_DISTRIBUTESHARDSLIKE

Will be raised if one tries to create a collection with a distributeShardsLike attribute which points to another collection that also has one.

1485 - ERROR_CLUSTER_MUST_NOT_DROP_COLL_OTHER_DISTRIBUTESHARDSLIKE

Will be raised if one tries to drop a collection to which another collection points with its distributeShardsLike attribute.

1486 - ERROR_CLUSTER_UNKNOWN_DISTRIBUTESHARDSLIKE

Will be raised if one tries to create a collection which points to an unknown collection in its distributeShardsLike attribute.

1487 - ERROR_CLUSTER_INSUFFICIENT_DBSERVERS

Will be raised if one tries to create a collection with a replicationFactor or writeConcern value greater than the available number of DB-Servers.

1488 - ERROR_CLUSTER_COULD_NOT_DROP_FOLLOWER

Will be raised if a follower that ought to be dropped could not be dropped in the Agency (under Current).

1489 - ERROR_CLUSTER_SHARD_LEADER_REFUSES_REPLICATION

Will be raised if a replication operation is refused by a shard leader.

1490 - ERROR_CLUSTER_SHARD_FOLLOWER_REFUSES_OPERATION

Will be raised if a replication operation is refused by a shard follower because it is coming from the wrong leader.

1491 - ERROR_CLUSTER_SHARD_LEADER_RESIGNED

Will be raised if a non-replication operation is refused by a former shard leader that has found out that it is no longer the leader.

1492 - ERROR_CLUSTER_AGENCY_COMMUNICATION_FAILED

Will be raised if after various retries an Agency operation could not be performed successfully.

1495 - ERROR_CLUSTER_LEADERSHIP_CHALLENGE_ONGOING

Will be raised when servers are currently competing for leadership, and the result is still unknown.

1496 - ERROR_CLUSTER_NOT_LEADER

Will be raised when an operation is sent to a non-leading server.

1497 - ERROR_CLUSTER_COULD_NOT_CREATE_VIEW_IN_PLAN

Will be raised when a Coordinator in a cluster cannot create an entry for a new View in the Plan hierarchy in the Agency.

1498 - ERROR_CLUSTER_VIEW_ID_EXISTS

Will be raised when a Coordinator in a cluster tries to create a View and the View ID already exists.

1499 - ERROR_CLUSTER_COULD_NOT_DROP_COLLECTION

Will be raised when a Coordinator in a cluster cannot drop a collection entry in the Plan hierarchy in the Agency.

ArangoDB query errors

1500 - ERROR_QUERY_KILLED

Will be raised when a running query is killed by an explicit admin command.

1501 - ERROR_QUERY_PARSE

Will be raised when query is parsed and is found to be syntactically invalid.

1502 - ERROR_QUERY_EMPTY

Will be raised when an empty query is specified.

1503 - ERROR_QUERY_SCRIPT

Will be raised when a runtime error is caused by the query.

1504 - ERROR_QUERY_NUMBER_OUT_OF_RANGE

Will be raised when a number is outside the expected range.

1505 - ERROR_QUERY_INVALID_GEO_VALUE

Will be raised when a geo index coordinate is invalid or out of range.

1510 - ERROR_QUERY_VARIABLE_NAME_INVALID

Will be raised when an invalid variable name is used.

1511 - ERROR_QUERY_VARIABLE_REDECLARED

Will be raised when a variable gets re-assigned in a query.

1512 - ERROR_QUERY_VARIABLE_NAME_UNKNOWN

Will be raised when an unknown variable is used or the variable is undefined the context it is used.

1521 - ERROR_QUERY_COLLECTION_LOCK_FAILED

Will be raised when a read lock on the collection cannot be acquired.

1522 - ERROR_QUERY_TOO_MANY_COLLECTIONS

Will be raised when the number of collections or shards in a query is beyond the allowed value.

1524 - ERROR_QUERY_TOO_MUCH_NESTING

Will be raised when a query contains expressions or other constructs with too many objects or that are too deeply nested.

1539 - ERROR_QUERY_INVALID_OPTIONS_ATTRIBUTE

Will be raised when an unknown attribute name or an invalid attribute value is used inside an OPTIONS clause.

1540 - ERROR_QUERY_FUNCTION_NAME_UNKNOWN

Will be raised when an undefined function is called.

1541 - ERROR_QUERY_FUNCTION_ARGUMENT_NUMBER_MISMATCH

Will be raised when the number of arguments used in a function call does not match the expected number of arguments for the function.

1542 - ERROR_QUERY_FUNCTION_ARGUMENT_TYPE_MISMATCH

Will be raised when the type of an argument used in a function call does not match the expected argument type.

1543 - ERROR_QUERY_INVALID_REGEX

Will be raised when an invalid regex argument value is used in a call to a function that expects a regex.

1550 - ERROR_QUERY_BIND_PARAMETERS_INVALID

Will be raised when the structure of bind parameters passed has an unexpected format.

1551 - ERROR_QUERY_BIND_PARAMETER_MISSING

Will be raised when a bind parameter was declared in the query but the query is being executed with no value for that parameter.

1552 - ERROR_QUERY_BIND_PARAMETER_UNDECLARED

Will be raised when a value gets specified for an undeclared bind parameter.

1553 - ERROR_QUERY_BIND_PARAMETER_TYPE

Will be raised when a bind parameter has an invalid value or type.

1561 - ERROR_QUERY_INVALID_ARITHMETIC_VALUE

Will be raised when a non-numeric value is used in an arithmetic operation.

1562 - ERROR_QUERY_DIVISION_BY_ZERO

Will be raised when there is an attempt to divide by zero.

1563 - ERROR_QUERY_ARRAY_EXPECTED

Will be raised when a non-array operand is used for an operation that expects an array argument operand.

1568 - ERROR_QUERY_COLLECTION_USED_IN_EXPRESSION

Will be raised when a collection is used as an operand in an AQL expression.

1569 - ERROR_QUERY_FAIL_CALLED

Will be raised when the function FAIL() is called from inside a query.

1570 - ERROR_QUERY_GEO_INDEX_MISSING

Will be raised when a geo restriction was specified but no suitable geo index is found to resolve it.

1571 - ERROR_QUERY_FULLTEXT_INDEX_MISSING

Will be raised when a fulltext query is performed on a collection without a suitable fulltext index.

1572 - ERROR_QUERY_INVALID_DATE_VALUE

Will be raised when a value cannot be converted to a date.

1573 - ERROR_QUERY_MULTI_MODIFY

Will be raised when an AQL query contains more than one data-modifying operation.

1574 - ERROR_QUERY_INVALID_AGGREGATE_EXPRESSION

Will be raised when an AQL query contains an invalid aggregate expression.

1575 - ERROR_QUERY_COMPILE_TIME_OPTIONS

Will be raised when an AQL query contains OPTIONS that cannot be figured out at query compile time.

1576 - ERROR_QUERY_DNF_COMPLEXITY

Will be raised internally when a too complex FILTER/PRUNE condition is encountered during the DNF conversion of the condition.

1577 - ERROR_QUERY_FORCED_INDEX_HINT_UNUSABLE

Will be raised when forceIndexHint is specified, and the hint cannot be used to serve the query.

1578 - ERROR_QUERY_DISALLOWED_DYNAMIC_CALL

Will be raised when a dynamic function call is made to a function that cannot be called dynamically.

1579 - ERROR_QUERY_ACCESS_AFTER_MODIFICATION

Will be raised when collection data are accessed after a data-modification operation.

AQL user function errors

1580 - ERROR_QUERY_FUNCTION_INVALID_NAME

Will be raised when a user function with an invalid name is registered.

1581 - ERROR_QUERY_FUNCTION_INVALID_CODE

Will be raised when a user function is registered with invalid code.

1582 - ERROR_QUERY_FUNCTION_NOT_FOUND

Will be raised when a user function is accessed but not found.

1583 - ERROR_QUERY_FUNCTION_RUNTIME_ERROR

Will be raised when a user function throws a runtime exception.

AQL query registry errors

1590 - ERROR_QUERY_BAD_JSON_PLAN

Will be raised when an HTTP API for a query got an invalid JSON object.

1591 - ERROR_QUERY_NOT_FOUND

Will be raised when an Id of a query is not found by the HTTP API.

1593 - ERROR_QUERY_USER_ASSERT

Will be raised if and user provided expression fails to evaluate to true

1594 - ERROR_QUERY_USER_WARN

Will be raised if and user provided expression fails to evaluate to true

1595 - ERROR_QUERY_WINDOW_AFTER_MODIFICATION

Will be raised when a window node is created after a data-modification operation.

ArangoDB cursor errors

1600 - ERROR_CURSOR_NOT_FOUND

Will be raised when a cursor is requested via its id but a cursor with that id cannot be found.

1601 - ERROR_CURSOR_BUSY

Will be raised when a cursor is requested via its id but a concurrent request is still using the cursor.

ArangoDB schema validation errors

1620 - ERROR_VALIDATION_FAILED

Will be raised when a document does not pass schema validation.

1621 - ERROR_VALIDATION_BAD_PARAMETER

Will be raised when the schema description is invalid.

ArangoDB transaction errors

1650 - ERROR_TRANSACTION_INTERNAL

Will be raised when a wrong usage of transactions is detected. this is an internal error and indicates a bug in ArangoDB.

1651 - ERROR_TRANSACTION_NESTED

Will be raised when transactions are nested.

1652 - ERROR_TRANSACTION_UNREGISTERED_COLLECTION

Will be raised when a collection is used in the middle of a transaction but was not registered at transaction start.

1653 - ERROR_TRANSACTION_DISALLOWED_OPERATION

Will be raised when a disallowed operation is carried out in a transaction.

1654 - ERROR_TRANSACTION_ABORTED

Will be raised when a transaction was aborted.

1655 - ERROR_TRANSACTION_NOT_FOUND

Will be raised when a transaction was not found.

User management errors

1700 - ERROR_USER_INVALID_NAME

Will be raised when an invalid user name is used.

1702 - ERROR_USER_DUPLICATE

Will be raised when a user name already exists.

1703 - ERROR_USER_NOT_FOUND

Will be raised when a user name is updated that does not exist.

1705 - ERROR_USER_EXTERNAL

Will be raised when the user is authenticated by an external server.

Service management errors (legacy)

1752 - ERROR_SERVICE_DOWNLOAD_FAILED

Will be raised when a service download from the central repository failed.

1753 - ERROR_SERVICE_UPLOAD_FAILED

Will be raised when a service upload from the client to the ArangoDB server failed.

Task errors

1850 - ERROR_TASK_INVALID_ID

Will be raised when a task is created with an invalid id.

1851 - ERROR_TASK_DUPLICATE_ID

Will be raised when a task id is created with a duplicate id.

1852 - ERROR_TASK_NOT_FOUND

Will be raised when a task with the specified id could not be found.

Graph / traversal errors

1901 - ERROR_GRAPH_INVALID_GRAPH

Will be raised when an invalid name is passed to the server.

1906 - ERROR_GRAPH_INVALID_EDGE

Will be raised when an invalid edge id is passed to the server.

1910 - ERROR_GRAPH_INVALID_FILTER_RESULT

Will be raised when an invalid filter result is returned in a graph traversal.

1920 - ERROR_GRAPH_COLLECTION_MULTI_USE

an edge collection may only be used once in one edge definition of a graph.

1921 - ERROR_GRAPH_COLLECTION_USE_IN_MULTI_GRAPHS

is already used by another graph in a different edge definition.

1922 - ERROR_GRAPH_CREATE_MISSING_NAME

a graph name is required to create or drop a graph.

1923 - ERROR_GRAPH_CREATE_MALFORMED_EDGE_DEFINITION

the edge definition is malformed. It has to be an array of objects.

1924 - ERROR_GRAPH_NOT_FOUND

a graph with this name could not be found.

1925 - ERROR_GRAPH_DUPLICATE

a graph with this name already exists.

1926 - ERROR_GRAPH_VERTEX_COL_DOES_NOT_EXIST

the specified vertex collection does not exist or is not part of the graph.

1927 - ERROR_GRAPH_WRONG_COLLECTION_TYPE_VERTEX

the collection is not a vertex collection.

1928 - ERROR_GRAPH_NOT_IN_ORPHAN_COLLECTION

Vertex collection not in list of orphan collections of the graph.

1929 - ERROR_GRAPH_COLLECTION_USED_IN_EDGE_DEF

The collection is already used in an edge definition of the graph.

1930 - ERROR_GRAPH_EDGE_COLLECTION_NOT_USED

The edge collection is not used in any edge definition of the graph.

1932 - ERROR_GRAPH_NO_GRAPH_COLLECTION

collection _graphs does not exist.

1935 - ERROR_GRAPH_INVALID_NUMBER_OF_ARGUMENTS

Invalid number of arguments. Expected:

1936 - ERROR_GRAPH_INVALID_PARAMETER

Invalid parameter type.

1938 - ERROR_GRAPH_COLLECTION_USED_IN_ORPHANS

The collection is already used in the orphans of the graph.

1939 - ERROR_GRAPH_EDGE_COL_DOES_NOT_EXIST

the specified edge collection does not exist or is not part of the graph.

1940 - ERROR_GRAPH_EMPTY

The requested graph has no edge collections.

1941 - ERROR_GRAPH_INTERNAL_DATA_CORRUPT

The _graphs collection contains invalid data.

1942 - ERROR_GRAPH_MUST_NOT_DROP_COLLECTION

The collection must not be dropped while it is used as part of at least one graph definition.

1943 - ERROR_GRAPH_CREATE_MALFORMED_ORPHAN_LIST

the orphan list argument is malformed. It has to be an array of strings.

1944 - ERROR_GRAPH_EDGE_DEFINITION_IS_DOCUMENT

the collection used as a relation is existing, but is a document collection, it cannot be used here.

1945 - ERROR_GRAPH_COLLECTION_IS_INITIAL

the collection is used as the initial collection of this graph and is not allowed to be removed manually.

1946 - ERROR_GRAPH_NO_INITIAL_COLLECTION

during the graph creation process no collection could be selected as the needed initial collection. Happens if a distributeShardsLike or replicationFactor mismatch was found.

1947 - ERROR_GRAPH_REFERENCED_VERTEX_COLLECTION_NOT_PART_OF_THE_GRAPH

the _from or _to collection specified for the edge refers to a vertex collection which is not used in any edge definition of the graph.

1948 - ERROR_GRAPH_NEGATIVE_EDGE_WEIGHT

a negative edge weight was found during a weighted graph traversal or shortest path query

1949 - ERROR_GRAPH_COLLECTION_NOT_PART_OF_THE_GRAPH

The collection is not used in any edge definition or as an orphan collection.

Session errors

1950 - ERROR_SESSION_UNKNOWN

Will be raised when an invalid/unknown session id is passed to the server.

1951 - ERROR_SESSION_EXPIRED

Will be raised when a session is expired.

Simple Client errors

2000 - ERROR_SIMPLE_CLIENT_UNKNOWN_ERROR

This error should not happen.

2001 - ERROR_SIMPLE_CLIENT_COULD_NOT_CONNECT

Will be raised when the client could not connect to the server.

2002 - ERROR_SIMPLE_CLIENT_COULD_NOT_WRITE

Will be raised when the client could not write data.

2003 - ERROR_SIMPLE_CLIENT_COULD_NOT_READ

Will be raised when the client could not read data.

2019 - ERROR_WAS_ERLAUBE

Will be raised if was erlaube?!

internal AQL errors

2200 - ERROR_INTERNAL_AQL

Internal error during AQL execution

Foxx management errors

3000 - ERROR_MALFORMED_MANIFEST_FILE

The service manifest file is not well-formed JSON.

3001 - ERROR_INVALID_SERVICE_MANIFEST

The service manifest contains invalid values.

3002 - ERROR_SERVICE_FILES_MISSING

The service folder or bundle does not exist on this server.

3003 - ERROR_SERVICE_FILES_OUTDATED

The local service bundle does not match the checksum in the database.

3004 - ERROR_INVALID_FOXX_OPTIONS

The service options contain invalid values.

3007 - ERROR_INVALID_MOUNTPOINT

The service mountpath contains invalid characters.

3009 - ERROR_SERVICE_NOT_FOUND

No service found at the given mountpath.

3010 - ERROR_SERVICE_NEEDS_CONFIGURATION

The service is missing configuration or dependencies.

3011 - ERROR_SERVICE_MOUNTPOINT_CONFLICT

A service already exists at the given mountpath.

3012 - ERROR_SERVICE_MANIFEST_NOT_FOUND

The service directory does not contain a manifest file.

3013 - ERROR_SERVICE_OPTIONS_MALFORMED

The service options are not well-formed JSON.

3014 - ERROR_SERVICE_SOURCE_NOT_FOUND

The source path does not match a file or directory.

3015 - ERROR_SERVICE_SOURCE_ERROR

The source path could not be resolved.

3016 - ERROR_SERVICE_UNKNOWN_SCRIPT

The service does not have a script with this name.

3099 - ERROR_SERVICE_API_DISABLED

The API for managing Foxx services has been disabled on this server.

JavaScript module loader errors

3100 - ERROR_MODULE_NOT_FOUND

The module path could not be resolved.

3101 - ERROR_MODULE_SYNTAX_ERROR

The module could not be parsed because of a syntax error.

3103 - ERROR_MODULE_FAILURE

Failed to invoke the module in its context.

Enterprise Edition errors

4000 - ERROR_NO_SMART_COLLECTION

The requested collection needs to be smart, but it isn't.

4001 - ERROR_NO_SMART_GRAPH_ATTRIBUTE

The given document does not have the SmartGraph attribute set.

4002 - ERROR_CANNOT_DROP_SMART_COLLECTION

This smart collection cannot be dropped, it dictates sharding in the graph.

4003 - ERROR_KEY_MUST_BE_PREFIXED_WITH_SMART_GRAPH_ATTRIBUTE

In a smart vertex collection _key must be prefixed with the value of the SmartGraph attribute.

4004 - ERROR_ILLEGAL_SMART_GRAPH_ATTRIBUTE

The given smartGraph attribute is illegal and cannot be used for sharding. All system attributes are forbidden.

4005 - ERROR_SMART_GRAPH_ATTRIBUTE_MISMATCH

The SmartGraph attribute of the given collection does not match the SmartGraph attribute of the graph.

4006 - ERROR_INVALID_SMART_JOIN_ATTRIBUTE

Will be raised when the smartJoinAttribute declaration is invalid.

4007 - ERROR_KEY_MUST_BE_PREFIXED_WITH_SMART_JOIN_ATTRIBUTE

when using smartJoinAttribute for a collection, the shard key value must be prefixed with the value of the SmartJoin attribute.

4008 - ERROR_NO_SMART_JOIN_ATTRIBUTE

The given document does not have the required SmartJoin attribute set or it has an invalid value.

4009 - ERROR_CLUSTER_MUST_NOT_CHANGE_SMART_JOIN_ATTRIBUTE

Will be raised if there is an attempt to update the value of the smartJoinAttribute.

4010 - ERROR_INVALID_DISJOINT_SMART_EDGE

Will be raised if there is an attempt to create an edge between separated graph components.

4011 - ERROR_UNSUPPORTED_CHANGE_IN_SMART_TO_SATELLITE_DISJOINT_EDGE_DIRECTION

Switching back and forth between Satellite and Smart in Disjoint SmartGraph is not supported within a single AQL statement. Split into multiple statements.

Agency errors

20001 - ERROR_AGENCY_MALFORMED_GOSSIP_MESSAGE

Malformed gossip message.

20002 - ERROR_AGENCY_MALFORMED_INQUIRE_REQUEST

Malformed inquire request.

20011 - ERROR_AGENCY_INFORM_MUST_BE_OBJECT

The inform message in the Agency must be an object.

20012 - ERROR_AGENCY_INFORM_MUST_CONTAIN_TERM

The inform message in the Agency must contain a uint parameter 'term'.

20013 - ERROR_AGENCY_INFORM_MUST_CONTAIN_ID

The inform message in the Agency must contain a string parameter 'id'.

20014 - ERROR_AGENCY_INFORM_MUST_CONTAIN_ACTIVE

The inform message in the Agency must contain an array 'active'.

20015 - ERROR_AGENCY_INFORM_MUST_CONTAIN_POOL

The inform message in the Agency must contain an object 'pool'.

20016 - ERROR_AGENCY_INFORM_MUST_CONTAIN_MIN_PING

The inform message in the Agency must contain an object 'min ping'.

20017 - ERROR_AGENCY_INFORM_MUST_CONTAIN_MAX_PING

The inform message in the Agency must contain an object 'max ping'.

20018 - ERROR_AGENCY_INFORM_MUST_CONTAIN_TIMEOUT_MULT

The inform message in the Agency must contain an object 'timeoutMult'.

20021 - ERROR_AGENCY_CANNOT_REBUILD_DBS

Will be raised if the readDB or the spearHead cannot be rebuilt from the replicated log.

20030 - ERROR_AGENCY_MALFORMED_TRANSACTION

Malformed agency transaction.

Supervision errors

20501 - ERROR_SUPERVISION_GENERAL_FAILURE

General supervision failure.

Scheduler errors

21003 - ERROR_QUEUE_FULL

Will be returned if the scheduler queue is full.

21004 - ERROR_QUEUE_TIME_REQUIREMENT_VIOLATED

Will be returned if a request with a queue time requirement is set and it cannot be fulfilled.

21005 - ERROR_TOO_MANY_DETACHED_THREADS

Will be returned if a scheduler thread tries to detach itself but there are already too many detached scheduler threads.

Maintenance errors

6003 - ERROR_ACTION_UNFINISHED

This maintenance action is still processing

Backup/Restore errors

7001 - ERROR_HOT_BACKUP_INTERNAL

Failed to create hot backup set

7002 - ERROR_HOT_RESTORE_INTERNAL

Failed to restore to hot backup set

7003 - ERROR_BACKUP_TOPOLOGY

The hot backup set cannot be restored on non matching cluster topology

7004 - ERROR_NO_SPACE_LEFT_ON_DEVICE

No space left on device

7005 - ERROR_FAILED_TO_UPLOAD_BACKUP

Failed to upload hot backup set to remote target

7006 - ERROR_FAILED_TO_DOWNLOAD_BACKUP

Failed to download hot backup set from remote source

7007 - ERROR_NO_SUCH_HOT_BACKUP

Cannot find a hot backup set with this Id

7008 - ERROR_REMOTE_REPOSITORY_CONFIG_BAD

The configuration given for upload or download operation to/from remote hot backup repositories is wrong.

7009 - ERROR_LOCAL_LOCK_FAILED

Some of the DB-Servers cannot be reached for transaction locks.

7010 - ERROR_LOCAL_LOCK_RETRY

Some of the DB-Servers cannot be reached for transaction locks.

7011 - ERROR_HOT_BACKUP_CONFLICT

Conflict of multiple hot backup processes.

7012 - ERROR_HOT_BACKUP_DBSERVERS_AWOL

One or more DB-Servers could not be reached for hot backup inquiry

Plan Analyzers errors

7021 - ERROR_CLUSTER_COULD_NOT_MODIFY_ANALYZERS_IN_PLAN

Plan could not be modified while creating or deleting Analyzers revision

Licensing

9001 - ERROR_LICENSE_EXPIRED_OR_INVALID

The license has expired or is invalid.

9002 - ERROR_LICENSE_SIGNATURE_VERIFICATION

Verification of license failed.

9003 - ERROR_LICENSE_NON_MATCHING_ID

The ID of the license does not match the ID of this instance.

9004 - ERROR_LICENSE_FEATURE_NOT_ENABLED

The installed license does not cover this feature.

9005 - ERROR_LICENSE_RESOURCE_EXHAUSTED

The installed license does not cover a higher number of this resource.

9006 - ERROR_LICENSE_INVALID

The license does not hold features of an ArangoDB license.

9007 - ERROR_LICENSE_CONFLICT

The license has one or more inferior features.

9008 - ERROR_LICENSE_VALIDATION_FAILED

Could not verify the license's signature.