{"version":"2.1.281","anchor":"upload-announcement-recovers-after-a-create-conflict","canonical_anchor":"upload-announcement-recovers-after-a-create-conflict","heading":"Upload announcement recovers after a create conflict","tier":null,"area":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281\/e\/upload-announcement-recovers-after-a-create-conflict","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281","markdown":"### Upload announcement recovers after a create conflict\n\nAn upload announcement that hits a create conflict now checks its own journal and continues if it wrote it\n\n**What**\n\nBefore uploading, the client announces the upload. That announcement can clash with a record that already exists, because the step is only allowed to create a new record and never to overwrite one. When this clash happens, the client now reads its own journal (`readOwnJournal`). If that journal was written using the same announcement token, the client takes the journal's etag and carries on. An etag is a label that identifies one version of a stored file. Before this change, the client gave up.\n\n**Why**\n\nAn upload whose earlier attempt already got through no longer fails just because that first attempt's record is still there."}