{% extends "_layout.html" %} {% set title = "Not found" %} {% set status = "404 Not Found" %} {% set description = "The thing you asked for does not exist, or it exists and is not yours. Those are deliberately indistinguishable." %} {% block main %}
The thing you asked for does not exist, or it exists and is not yours. This page is here to tell you that those two cases are deliberately indistinguishable.
Check the identifier. If you are confident it is right and that you should have access, this is an access question for whoever administers your account — not something a retry or a different scope will resolve.
Do not infer from a 404 that a job id is free, unused, or invalid.
It means only that the server will not discuss it with you.
An API that answers 403 for exists, not yours and 404 for
does not exist has turned its identifier space into an oracle. Anyone holding a credential
could walk ids and learn which ones correspond to real jobs, whose existence is itself
information.
So the server collapses the two. You will see a 404 for:
…/logs for a node that has finished and kept no log, or whose
logs artifact’s bytes were deleted, and for a node the job does not have
once the job’s nodes are known;DELETE again;POST /v1/auth/browser that names nothing the caller can see;/v1 that no route serves, which is the same 404 in
application/problem+json, with this type.This costs you a clear error message in exactly one situation: when something really is yours and you have made a typo. That trade is accepted knowingly.
{
"type": "https://sc.example.com/server-errors/not-found",
"title": "Not found",
"status": 404,
"detail": "No such job.",
"instance": "/v1/jobs/01J9...",
"trace_id": "4bf92f3577b34da6a3ce929d0e0e4736"
}
No required extension members, and detail will not tell you which
case you are in. That is the whole point — a detail that leaked it would be a bug
worth reporting. The one exception is a create through a CI credential bound to a project: there
detail names the project the credential is bound to, and says its person is not a member
of it where that is why. That tells you nothing the credential did not already hold.
not-ready (409) is the interesting neighbour. Asking for a node’s
log before that node has started is not a 404: you have just read the
job object, so the job’s existence is not a secret, and the honest answer is that the state is
wrong rather than the identity. It carries Retry-After and you should retry.
The rule that separates them: 404 hides whether a thing exists.
409 is for when existence is already established and the state is the
problem.
entitlement-denied (403) is used
where existence is not secret — a PDK you may not use is named in your own manifest,
so refusing it plainly reveals nothing you did not already know.