Review and delivery
What we check before a release ships, why one gets held, and how delivery is tracked.
6 articles
All guides
6 articles- What our review checks The automated checks every release runs at submit, the difference between a hard failure and a flag, and why a person approves every release before it ships.
- Common rejection reasons, and how to fix them The findings that stop a release or flag it for a reviewer, what each one actually means, and the fix for each, grouped by metadata, audio, artwork and rights.
- Covers, remixes and samples: the documents we need Covers, remixes, samples and public-domain works all distribute through Run. What each one has to carry, where you attach it, and what is never accepted.
- Tracking delivery to the stores What each delivery state means, how your run.stream page connects pre-saves and streaming links, why stores go live at different times, and what to do when one lags behind.
- Your run.stream release link How your release gets a shareable link, what fans see before and after release day, and which audience counts Run keeps.
- Taking a release down How to request a takedown, how it moves store by store, what it does not undo, and how to handle an urgent copyright or impersonation case.