{"version":"2.1.319","anchor":"artifact-share-relay-errors-no-longer-return-an-http-status","canonical_anchor":"artifact-share-relay-errors-no-longer-return-an-http-status","heading":"Artifact sharing errors no longer include the web status code","tier":"notice","area":"Artifacts","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.319\/e\/artifact-share-relay-errors-no-longer-return-an-http-status","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.319","markdown":"### Artifact sharing errors no longer include the web status code\n\nWhen reading or confirming an artifact's sharing fails at the cloud relay, the error no longer carries the HTTP status code\n\n**What**\n\nTwo errors about sharing an artifact (something Claude made that can be shared) no longer carry the HTTP status code, the number a web server sends back to say what went wrong. They are the errors for failing to read an artifact's sharing settings and for failing to confirm a share. The message text is unchanged.\n\n**Why**\n\nThe error details are slightly less detailed than before.\n\n- Area: Artifacts\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 0\/5\n- Scope: individual\n- Heads-up: no"}