404

You may get a 404 response when reading an item that has been written to EdgeKV, due to the eventual consistency property of EdgeKV. You can read more about EdgeKV's eventual consistency model in the EdgeKV data model section.

These are the most common reasons for a 404 response when performing management operations:

• The EdgeKV database is not initialized.
• The requested access token was not found or there are no tokens under this account.

These are the most common reasons for a 404 response when performing data operations:

• The requested group was not found.
• The requested item was not found or the retention period set on the namespace may have elapsed since the item was last written or updated.

{
    "additionalDetail": {
        "detail": "Namespace is not found: bad_namespace",
        "instance": "/service/v1/s/5192145/namespaces/bad_namespace",
        "requestId": "5d424b9289ab9b43",
        "status": 404,
        "title": "NOT_FOUND"
    },
    "detail": "Unable to perform operation.",
    "instance": "2c82be29-f909-4d42-b775-de404e264fd9",
    "status": 404,
    "title": "Operation failed",
    "type": "https://problems.luna.akamaiapis.net/edgedb-api/operationFailed"
}