{"version":"2.1.232","anchor":"artifact-boot-failures-return-a-code-instead-of-reporting-in","canonical_anchor":"artifact-boot-failures-return-a-code-instead-of-reporting-in","heading":"Artifact boot failures return a code instead of reporting inline","tier":"internal","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.232\/e\/artifact-boot-failures-return-a-code-instead-of-reporting-in","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.232","markdown":"### Artifact boot failures return a code instead of reporting inline\n\nArtifact startup failures return an error code and let the caller report it.\n\n**What**\n\nThe artifact boot path no longer fires telemetry at each failure site; it returns an error code alongside the error and leaves reporting to the caller.\n\n**Details**\n\n- Codes are `boot_request_error`, `boot_404`, `boot_failed`, `boot_incomplete`, or the failure reason with dashes replaced by underscores.\n- The unauthenticated case builds its message through a helper instead of an inline string.\n\n**Evidence**\n\n`boot_incomplete`\n\n- Area: Artifacts\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}