{"version":"2.1.267","anchor":"artifact-publish-gained-expanded-per-reason-code-error-mess","canonical_anchor":"artifact-publish-gained-expanded-per-reason-code-error-mess","heading":"Artifact publish gained expanded, per-reason-code error messages","tier":"notice","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.267\/e\/artifact-publish-gained-expanded-per-reason-code-error-mess","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.267","markdown":"### Artifact publish gained expanded, per-reason-code error messages\n\nArtifact publish failures now show specific, tailored error messages for many more failure reasons\n\n**What**\n\nArtifact publishing (deploying) failures now come with much more specific error messages. A large new table of reason codes, covering cases like `audience_conflict`, `capability_refused`, `contract_refused`, `not_owner`, `read_timeout`, `deadline_invalid`, and `live_path_cap`, drives custom explanatory text instead of a small set of generic hardcoded checks. A new `deadline_invalid` case automatically retries the request with its `deadline` field removed, and errors about specific declared capabilities now get their own tailored messages.\n\n**Why**\n\nThis makes it much clearer why a publish attempt failed, rather than showing a generic error for many different underlying problems.\n\n- Area: Artifacts\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5"}