ResourceNotFound

Andromeda answers 404 with the problem type https://uri.etsi.org/ngsi-ld/errors/ResourceNotFound. The resource the request names doesn't exist, and nothing was changed. A delete of something already gone ends here too. The specification defines this type and binds it to 404.

When this comes back

• The entity doesn't exist, on retrieve, replace, merge, delete, or any operation that addresses it in the path.
• An attribute the entity doesn't have, on a partial update, replace or merge against it. Merge adds attributes at the entity level, but a fragment against a missing attribute path is still not found. See Merge and replace.
• A datasetId naming no instance of the attribute, or a temporal instanceId naming an instance that is already gone. See Dataset ids.
• A discovery attribute whose last instance is gone, whether it was deleted or removed by the expiry sweep. See Discovery.
• The NGSILD-Snapshot header naming no Snapshot in the tenant, a Snapshot purge filter that selects nothing, or a clone of a Snapshot that doesn't exist. See Snapshots.
• A stored @context identifier that doesn't exist.

A tenant that doesn't exist answers NonexistentTenant instead.

One more case comes from federation. When an exclusive or redirect registration makes one context source the only holder of a resource, and that source answers 404 for it, Andromeda passes the 404 through with this type. See When the one source fails.