Error codes and meanings

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 unencountered.

  • 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-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.

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.

  • 412 - ERROR_HTTP_PRECONDITION_FAILED
    Will be raised when a precondition for an HTTP request is not met.

  • 500 - ERROR_HTTP_SERVER_ERROR
    Will be raised when an internal server is encountered.

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

For errors that occur because of a programming error.

  • 1000 - ERROR_ARANGO_ILLEGAL_STATE
    Internal error that will be raised when the datafile is not in the required state.

  • 1002 - ERROR_ARANGO_DATAFILE_SEALED
    Internal error that will be raised when trying to write to a datafile.

  • 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.

  • 1006 - ERROR_ARANGO_DATAFILE_UNREADABLE
    Internal error that will be raised when a datafile is unreadable.

  • 1007 - ERROR_ARANGO_DATAFILE_EMPTY
    Internal error that will be raised when a datafile is empty.

  • 1008 - ERROR_ARANGO_RECOVERY
    Will be raised when an error occurred during WAL log file recovery.

  • 1009 - ERROR_ARANGO_DATAFILE_STATISTICS_NOT_FOUND
    Will be raised when a required datafile statistics object was not found.

External ArangoDB storage errors

For errors that occur because of an outside event.

  • 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.

  • 1103 - ERROR_ARANGO_MMAP_FAILED
    Will be raised when the system call mmap failed.

  • 1104 - ERROR_ARANGO_FILESYSTEM_FULL
    Will be raised when the filesystem is full.

  • 1105 - ERROR_ARANGO_NO_JOURNAL
    Will be raised when a journal cannot be created.

  • 1106 - ERROR_ARANGO_DATAFILE_ALREADY_EXISTS
    Will be raised when the datafile cannot be created or renamed because a file of the same name already exists.

  • 1107 - ERROR_ARANGO_DATADIR_LOCKED
    Will be raised when the database directory is locked by a different process.

  • 1108 - ERROR_ARANGO_COLLECTION_DIRECTORY_ALREADY_EXISTS
    Will be raised when the collection cannot be created because a directory of the same name already exists.

  • 1109 - ERROR_ARANGO_MSYNC_FAILED
    Will be raised when the system call msync failed.

  • 1110 - ERROR_ARANGO_DATADIR_UNLOCKABLE
    Will be raised when the server cannot lock the database directory on startup.

  • 1111 - ERROR_ARANGO_SYNC_TIMEOUT
    Will be raised when the server waited too long for a datafile to be synced to disk.

General ArangoDB storage errors

For errors that occur when fulfilling a user request.

  • 1200 - ERROR_ARANGO_CONFLICT
    Will be raised when updating or deleting a document and a conflict has been detected.

  • 1201 - ERROR_ARANGO_DATADIR_INVALID
    Will be raised when a non-existing database directory was specified when starting the database.

  • 1202 - ERROR_ARANGO_DOCUMENT_NOT_FOUND
    Will be raised when a document with a given identifier or handle is unknown.

  • 1203 - ERROR_ARANGO_COLLECTION_NOT_FOUND
    Will be raised when a collection with a 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 handle is corrupt.

  • 1206 - ERROR_ARANGO_MAXIMAL_SIZE_TOO_SMALL
    Will be raised when the maximal size of the journal is too small.

  • 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 handle 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.

  • 1217 - ERROR_ARANGO_COLLECTION_NOT_UNLOADED
    Will be raised when a collection should be unloaded, but has a different status.

  • 1218 - ERROR_ARANGO_COLLECTION_TYPE_INVALID
    Will be raised when an invalid collection type is used in a request.

  • 1219 - ERROR_ARANGO_VALIDATION_FAILED
    Will be raised when the validation of an attribute of a structure failed.

  • 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.

  • 1231 - ERROR_ARANGO_ENDPOINT_NOT_FOUND
    Will be raised when there is an attempt to delete a non-existing endpoint.

  • 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.

  • 1234 - ERROR_ARANGO_INDEX_DOCUMENT_ATTRIBUTE_MISSING
    Will be raised when an attempt to insert a document into an index is caused by in the document not having one or more attributes which the index is built on.

  • 1235 - ERROR_ARANGO_INDEX_CREATION_FAILED
    Will be raised when an attempt to create an index has failed.

  • 1236 - ERROR_ARANGO_WRITE_THROTTLE_TIMEOUT
    Will be raised when the server is write-throttled and a write operation has waited too long for the server to process queued operations.

  • 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.

Checked ArangoDB storage errors

For errors that occur but are anticipated.

  • 1300 - ERROR_ARANGO_DATAFILE_FULL
    Will be raised when the datafile reaches its limit.

  • 1301 - ERROR_ARANGO_EMPTY_DATADIR
    Will be raised when encountering an empty server database directory.

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 master.

  • 1401 - ERROR_REPLICATION_INVALID_RESPONSE
    Will be raised when the replication applier receives an invalid response from the master.

  • 1402 - ERROR_REPLICATION_MASTER_ERROR
    Will be raised when the replication applier receives a server error from the master.

  • 1403 - ERROR_REPLICATION_MASTER_INCOMPATIBLE
    Will be raised when the replication applier connects to a master that has an incompatible version.

  • 1404 - ERROR_REPLICATION_MASTER_CHANGE
    Will be raised when the replication applier connects to a different master 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.

  • 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.

ArangoDB cluster errors

  • 1450 - ERROR_CLUSTER_NO_AGENCY
    Will be raised when none of the agency servers can be connected to.

  • 1451 - ERROR_CLUSTER_NO_COORDINATOR_HEADER
    Will be raised when a DB server in a cluster receives a HTTP request without a coordinator header.

  • 1452 - ERROR_CLUSTER_COULD_NOT_LOCK_PLAN
    Will be raised when a coordinator in a cluster cannot lock the Plan hierarchy in the agency.

  • 1453 - ERROR_CLUSTER_COLLECTION_ID_EXISTS
    Will be raised when a coordinator in a cluster tries to create a collection and the collection ID already exists.

  • 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.

  • 1455 - ERROR_CLUSTER_COULD_NOT_READ_CURRENT_VERSION
    Will be raised when a coordinator in a cluster cannot read the Version entry in the Current hierarchy in the agency.

  • 1456 - ERROR_CLUSTER_COULD_NOT_CREATE_COLLECTION
    Will be raised when a coordinator in a cluster notices that some DBServers 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.

  • 1459 - ERROR_CLUSTER_COULD_NOT_REMOVE_COLLECTION_IN_CURRENT
    Will be raised when a coordinator in a cluster cannot remove an entry for a collection in the Current 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 DBServers 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 DBserver 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 DBserver cannot read the Plan in the agency.

  • 1473 - ERROR_CLUSTER_COULD_NOT_TRUNCATE_COLLECTION
    Will be raised if a coordinator cannot truncate all shards of a cluster collection.

  • 1474 - ERROR_CLUSTER_AQL_COMMUNICATION
    Will be raised if the internal communication of the cluster for AQL produces an error.

  • 1475 - ERROR_ARANGO_DOCUMENT_NOT_FOUND_OR_SHARDING_ATTRIBUTES_CHANGED
    Will be raised when a document with a given identifier or handle is unknown, or if the sharding attributes have been changed in a REPLACE operation in the cluster.

  • 1476 - ERROR_CLUSTER_COULD_NOT_DETERMINE_ID
    Will be raised if a cluster server at startup could not determine its own ID from the local info provided.

  • 1477 - ERROR_CLUSTER_ONLY_ON_DBSERVER
    Will be raised if there is an attempt to run a DBserver-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.

  • 1479 - ERROR_CLUSTER_UNKNOWN_CALLBACK_ENDPOINT
    An endpoint couldn't be found

  • 1480 - ERROR_CLUSTER_AGENCY_STRUCTURE_INVALID
    The structure in the agency is invalid

  • 1481 - ERROR_CLUSTER_AQL_COLLECTION_OUT_OF_SYNC
    Will be raised if a collection needed during query execution is out of sync. This currently can only happen when using satellite collections

  • 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.

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.

  • 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 in a query is beyond the allowed value.

  • 1530 - ERROR_QUERY_DOCUMENT_ATTRIBUTE_REDECLARED
    Will be raised when a document attribute is re-assigned.

  • 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.

  • 1560 - ERROR_QUERY_INVALID_LOGICAL_VALUE
    Will be raised when a non-boolean value is used in a logical operation.

  • 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.

  • 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 data-modification query contains options that cannot be figured out at query compile time.

  • 1576 - ERROR_QUERY_EXCEPTION_OPTIONS
    Will be raised when an AQL data-modification query contains an invalid options specification.

  • 1577 - ERROR_QUERY_COLLECTION_USED_IN_EXPRESSION
    Will be raised when a collection is used as an operand in an AQL expression.

  • 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.

  • 1592 - ERROR_QUERY_IN_USE
    Will be raised when an Id of a query is found by the HTTP API but the query is in use.

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 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.

User management errors

  • 1700 - ERROR_USER_INVALID_NAME
    Will be raised when an invalid user name is used.

  • 1701 - ERROR_USER_INVALID_PASSWORD
    Will be raised when an invalid password 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.

  • 1704 - ERROR_USER_CHANGE_PASSWORD
    Will be raised when the user must change his password.

Service management errors (legacy)

These have been superceded by the Foxx management errors in public APIs.

  • 1750 - ERROR_SERVICE_INVALID_NAME
    Will be raised when an invalid service name is specified.

  • 1751 - ERROR_SERVICE_INVALID_MOUNT
    Will be raised when an invalid mount is specified.

  • 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.

  • 1902 - ERROR_GRAPH_COULD_NOT_CREATE_GRAPH
    Will be raised when an invalid name, vertices or edges is passed to the server.

  • 1903 - ERROR_GRAPH_INVALID_VERTEX
    Will be raised when an invalid vertex id is passed to the server.

  • 1904 - ERROR_GRAPH_COULD_NOT_CREATE_VERTEX
    Will be raised when the vertex could not be created.

  • 1905 - ERROR_GRAPH_COULD_NOT_CHANGE_VERTEX
    Will be raised when the vertex could not be changed.

  • 1906 - ERROR_GRAPH_INVALID_EDGE
    Will be raised when an invalid edge id is passed to the server.

  • 1907 - ERROR_GRAPH_COULD_NOT_CREATE_EDGE
    Will be raised when the edge could not be created.

  • 1908 - ERROR_GRAPH_COULD_NOT_CHANGE_EDGE
    Will be raised when the edge could not be changed.

  • 1909 - ERROR_GRAPH_TOO_MANY_ITERATIONS
    Will be raised when too many iterations are done in a graph traversal.

  • 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 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 orphan collection 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.,

  • 1931 - ERROR_GRAPH_NOT_AN_ARANGO_COLLECTION
    The collection is not an ArangoCollection.,

  • 1932 - ERROR_GRAPH_NO_GRAPH_COLLECTION
    collection _graphs does not exist.,

  • 1933 - ERROR_GRAPH_INVALID_EXAMPLE_ARRAY_OBJECT_STRING
    Invalid example type. Has to be String, Array or Object.,

  • 1934 - ERROR_GRAPH_INVALID_EXAMPLE_ARRAY_OBJECT
    Invalid example type. Has to be Array or Object.,

  • 1935 - ERROR_GRAPH_INVALID_NUMBER_OF_ARGUMENTS
    Invalid number of arguments. Expected: ,

  • 1936 - ERROR_GRAPH_INVALID_PARAMETER
    Invalid parameter type.,

  • 1937 - ERROR_GRAPH_INVALID_ID
    Invalid id,

  • 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.

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 - SIMPLE_CLIENT_UNKNOWN_ERROR
    This error should not happen.

  • 2001 - SIMPLE_CLIENT_COULD_NOT_CONNECT
    Will be raised when the client could not connect to the server.

  • 2002 - SIMPLE_CLIENT_COULD_NOT_WRITE
    Will be raised when the client could not write data.

  • 2003 - SIMPLE_CLIENT_COULD_NOT_READ
    Will be raised when the client could not read data.

Communicator errors

  • 2100 - COMMUNICATOR_REQUEST_ABORTED
    Request was aborted.

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.

  • 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.

JavaScript module loader errors

  • 3100 - ERROR_MODULE_NOT_FOUND
    The module path could not be resolved.

  • 3103 - ERROR_MODULE_FAILURE
    Failed to invoke the module in its context.

Enterprise errors

  • 4000 - ERROR_NO_SMART_COLLECTION
    The requested collection needs to be smart, but it ain't

  • 4001 - ERROR_NO_SMART_GRAPH_ATTRIBUTE
    The given document does not have the smart graph 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 smart graph attribute.

  • 4004 - ERROR_ILLEGAL_SMART_GRAPH_ATTRIBUTE
    The given smartGraph attribute is illegal and connot be used for sharding. All system attributes are forbidden.

Agency errors

  • 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'.

  • 20020 - ERROR_AGENCY_INQUIRE_CLIENT_ID_MUST_BE_STRING
    Inquiry by clientId failed

Supervision errors

  • 20501 - ERROR_SUPERVISION_GENERAL_FAILURE
    General supervision failure.

Dispatcher errors

  • 21001 - ERROR_DISPATCHER_IS_STOPPING
    Will be returned if a shutdown is in progress.

  • 21002 - ERROR_QUEUE_UNKNOWN
    Will be returned if a queue with this name does not exist.

  • 21003 - ERROR_QUEUE_FULL
    Will be returned if a queue with this name is full.