Editing, reopening and resubmitting

A release is editable while it is a draft, and only then. The moment you submit it, every field locks: the checks and the review have to look at one fixed version of the release, not one that moves under them.

That does not mean a mistake is final. If the checks stop your release, or a reviewer refuses it, you reopen it back to a draft, fix what was wrong and submit it again. Reopening does not cost you another release from your plan allowance.

Editing a draft

Open the release from your releases and choose “Continue editing”. Everything is open: metadata, artists, tracks, files, store selection. Changes save as you go, and “Save draft” writes the release section on demand.

Deleting a draft is permanent. Drafts are not capped on any plan: only submitting a release counts against an allowance, so there is nothing to free by deleting one.

Reopening a release that failed checks or was refused

On the release page, “Fix & edit” puts the release back to draft and opens the editor. It also clears the previous verdict, so you start the cycle clean.

• Checks failed means the automated checks found something they will not pass. The findings are listed on the release page with the reason for each one. See why a release gets held or refused.
• Rejected means a person reviewed it and refused it, with a written reason. Nothing was sent to any store.

Fix the specific items, then submit again. The release walks the same path as a first submission: checks, then review.

Reopen it, do not delete it. Your release allowance is counted once per release, the first time it is submitted. Reopening, fixing and resubmitting the same release never spends a second one, but deleting a submitted release does not give the allowance back. If you mean to try again, reopen and fix it rather than starting over.

Withdrawing before delivery

Until a release has been handed to the stores, you can remove it from Run entirely. The release page offers “Delete draft” while it is still a draft, and “Withdraw & delete” once it has been submitted. Either is permanent and takes the uploaded files with it.

Once the release is approved and moving, that option closes. If you need to stop a release that is already delivering, open a support request rather than waiting for it to land.

After a release has been delivered

A delivered release cannot be edited or deleted in Run. Two things follow from that:

• To remove it from the stores, request a takedown. See taking a release down.
• To correct something on a release that is already out, open a support request. Changes to a live release are handled case by case, because every change has to travel back out to every store.

Some things are fixed by design rather than by policy. The barcode identifies the release and the ISRCs identify the recordings; the stores use them to recognise the release you already put out. Replacing them creates a different release rather than correcting this one. See ISRCs and barcodes.

Changing an AI disclosure after delivery

Treat the three AI disclosures as something to settle before you submit. Changing one on a release that is already out is not a quiet metadata edit: it sends the release back through a fresh review in our distribution pipeline, and availability on the stores can be affected while that review runs.

If a disclosure was wrong, tell us anyway. An honest correction is always better than a wrong disclosure sitting on a live release. See AI disclosure.

The states a release moves through

The release page shows the current state, the reasons behind it, and whichever action is available to you at that point.