gRPC status 5: NOT_FOUND
NOT_FOUND is gRPC status code 5. The requested entity, such as a file, row or user, does not exist.
Updated
Usual causes
- The ID in the request does not exist, or was deleted.
- The request reached a different environment or database than you expected.
- The server returns
NOT_FOUNDrather thanPERMISSION_DENIEDto hide that the entity exists.
What to check
- The exact ID or name sent, including case and whitespace.
- Which server and environment the call reached.
- Whether the entity was created in the same transaction or region the read goes to.
Not to be confused with
A missing method or service is UNIMPLEMENTED, not NOT_FOUND.
What it looks like
A typical error, as a Go client prints it: rpc error: code = NotFound desc = user 42 not found
Retry, and the HTTP equivalent
| NOT_FOUND | |
|---|---|
| Code | 5 |
| Name | NOT_FOUND |
| In istek's status bar | not_found |
| Retry | Not unless the entity is expected to appear, such as right after an asynchronous create. |
| HTTP status | 404 |
istek names the status of every call it makes, not_found included, and explains transport failures in plain words. See istek.