{"version":"2.1.257","anchor":"artifact-comments-retryable-networkrelay-errors-now-flagge","canonical_anchor":"artifact-comments-retryable-networkrelay-errors-now-flagge","heading":"Artifact comments: retryable network\/relay errors now flagged explicitly","tier":"notice","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.257\/e\/artifact-comments-retryable-networkrelay-errors-now-flagge","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.257","markdown":"### Artifact comments: retryable network\/relay errors now flagged explicitly\n\nFetching artifact comments now flags retryable network and 429\/5xx failures and honors a Retry-After header.\n\nFetching artifact comments now distinguishes retryable failures, such as network errors, HTTP 429\/5xx, or relay-unavailable responses with certain statuses, from other failures via an explicit retryable flag, and honors a `Retry-After` header when present, instead of returning a generic failure uniformly.\n\n- Area: Artifacts\n- Names: `Retry-After`\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}