Music not live on release day? Check the delivery stage

Submitted, delivered and live are different

A saved draft is not a submitted release. A submitted release is not proof that every selected destination has received it, and delivery is not the same as public availability. Write down the last status you can actually confirm. Do not tell listeners a store is broken based only on a distributor-screen message.

Check the release you meant to find

• Confirm the release title, artist, intended date and relevant time zone.
• Open an exact release link if available; a name search may not identify a new release reliably.
• Check the intended artist profile as well as the release itself. Music on the wrong profile is a mapping problem.
• Record the affected platform and territory without assuming that another country or service has the same availability.
• Read any correction request and check whether the requested action was completed. Keep its case reference.

Understand the platform’s guidance

Spotify’s support guidance says new music needs processing time and directs artists with an unresolved delayed delivery to their distributor. It gives provider-side checks for ingestion errors, dates and territorial availability. Those are not controls every artist can access and do not establish a guaranteed DistroBolt turnaround. Ask the team to investigate the delivery record rather than attempting provider-only actions yourself.

Send a compact incident record

• Release reference, UPC and affected track ISRC where available.
• Intended release date and the date/time you checked.
• Destination and country where the problem was observed.
• Current status, exact message and any previous support case.
• A working link showing the issue, or a clear statement that no public link has been found.
• The specific question: delivery received, correction pending, wrong date, territory restriction or profile mapping?

A practical example

An EP is visible on one store but not another. The artist records both links, the intended date and the missing destination. DistroBolt can then investigate that delivery instead of receiving a vague “my music is gone” message. If the release exists under a similarly named artist, the artist instead supplies both profile links using the mapping guide. This keeps different problems from becoming conflicting correction requests.

Avoid changes that complicate the case

Do not create a second release with new identifiers merely to force availability. Do not request removal from the previous distributor during a catalogue move until the new deliveries have been checked and the transition coordinated. Update a promotional announcement honestly if the release is not yet verified, rather than promising a new date without confirmation.

Close the loop after a response

Check the real destination again, then report which links are resolved and which are still wrong. Keep release availability separate from royalty reporting: a live recording does not create an immediate payable balance. For the next release, use the release plan to allow time for preparation and corrections without treating a checklist as a guaranteed live date.