{"version":"2.1.170","anchor":"model-not-found-error-now-carries-notfound-flag","canonical_anchor":"model-not-found-error-now-carries-notfound-flag","heading":"Model Not Found Error Now Carries notFound Flag","tier":null,"area":null,"scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.170\/e\/model-not-found-error-now-carries-notfound-flag","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.170","markdown":"### Model Not Found Error Now Carries `notFound` Flag\n\nWhen model validation fails because the model ID was not found (HTTP 404 or message containing \"model:\"), the returned validation object now includes `notFound: true` in addition to the error string. This allows callers to distinguish \"not found\" from other validation failures.\n\n**Evidence**\n\nModel validation error handling (search for `\"notFound: !0\"`)"}