{"version":"2.1.267","anchor":"artifact-publish-preflight-now-recognizes-a-distinct-conten","canonical_anchor":"artifact-publish-preflight-now-recognizes-a-distinct-conten","heading":"Artifact publish preflight now recognizes a distinct \"content_pending\" refusal and auto-retries","tier":"notice","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.267\/e\/artifact-publish-preflight-now-recognizes-a-distinct-conten","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.267","markdown":"### Artifact publish preflight now recognizes a distinct \"content_pending\" refusal and auto-retries\n\nArtifact publishing now auto-retries on a specific 'content_pending' server refusal, not just unrecognized errors\n\n**What**\n\nWhen publishing an artifact (a generated file or document Claude Code creates and sends to a server), the server can reject the request with an HTTP 422 error. The retry logic that double-checks and resends after such a rejection now specifically recognizes a `content_pending` error code from the server, using a new step that extracts the status code from the response. Previously it only had a generic fallback for 422 responses it didn't recognize.\n\n**Why**\n\nThis makes automatic retries more reliable when the server reports the artifact's content simply isn't ready yet, rather than treating that case as just another unrecognized failure.\n\n- Area: Artifacts\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}