{"version":"2.1.293","anchor":"artifact-create-from-type-retries-gateway-busy-and-reports-r","canonical_anchor":"artifact-create-from-type-retries-gateway-busy-and-reports-r","heading":"Creating an artifact retries once when the relay is busy and gives clearer refusals","tier":"notice","area":"Artifacts","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.293\/e\/artifact-create-from-type-retries-gateway-busy-and-reports-r","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.293","markdown":"### Creating an artifact retries once when the relay is busy and gives clearer refusals\n\nArtifact creation through a gateway relay now waits and retries once when busy, and says when approval or policy refused it\n\n**What**\n\nCreating an artifact from a type can go through a gateway relay, a go-between service. Before, there was no retry and no specific refusal reasons. Now:\n\n- If the relay says it is busy and gives a wait time, Claude Code waits and tries once more.\n\n- If it is still busy, the result says the relay is busy.\n\n- A refusal because approval was not given is reported as such.\n\n- A refusal because of a policy is reported as such.\n\n- A \"cloud unavailable\" error now says whether it happened after the retry.\n\nA successfully created artifact also reports whether it was read, whether it was shared, and whether its manifest (its description file) was left unread.\n\n**Why**\n\nArtifact creation through a relay now recovers from a brief busy response, and when it fails it says why more clearly.\n\n- Area: Artifacts\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}