For REST requests, I observed that we use EntityNotFound for 3 cases - a) Invalid Entity name (actual case where returning EntityNotFound is accurate), b) Item identified by PK is not present, c) Invalid PK field (the specified PK fields are not present in the entity definition) in the request.

Introduce appropriate sub status codes that can be returned with exceptions so that it is beneficial for users to help them with an actionable item.