gRPC
5 NOT_FOUND
Some requested entity was not found. For example, a file or directory that the RPC was supposed to operate on does not exist.
When You See This Code
The resource referenced in the request doesn't exist — such as looking up a user by ID that has been deleted or never created.
How to Fix
Verify the resource identifier is correct. Ensure the resource was created before accessing it, or handle the not-found case gracefully in your client.
Specification
View RFC / Specification →Cross-Protocol Equivalents
Comparisons
Guides
Choosing the Right HTTP Status Codes for REST APIs
API Design
gRPC Status Codes: A Practical Guide
API Design
Debugging Timeout Errors: 408 and 504
Debugging & Troubleshooting
How to Implement and Handle Rate Limiting (429)
API Design
API Versioning Strategies: URL, Header, and Query Param
API Design
Designing Consistent API Error Responses
API Design
API Keys vs OAuth vs JWT: Choosing the Right Auth Method
Security & Authentication