{"version":"2.1.275","anchor":"artifact-asset-upload-retries-are-now-flagged-as-resent","canonical_anchor":"artifact-asset-upload-retries-are-now-flagged-as-resent","heading":"Artifact asset upload retries are now flagged as resent","tier":"internal","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.275\/e\/artifact-asset-upload-retries-are-now-flagged-as-resent","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.275","markdown":"### Artifact asset upload retries are now flagged as `resent`\n\nRetried artifact file uploads are now explicitly marked as resent in the results\n\n**What**\n\nWhen Claude Code retries uploading a file (an asset) attached to an artifact, both the success and error outcomes of that retry now carry a `resent` marker. This marker is also recorded consistently in the background usage tracking (telemetry) even when the upload fails early.\n\n**Why**\n\nThis makes it possible to tell, from the result of an upload, whether it happened on a first try or a retry, which helps in diagnosing upload issues and understanding retry behavior.\n\n- Area: Artifacts\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}