Troubleshooting

Every message we refuse comes back with a reason in plain words: in the acknowledgement file's ErrorText, and in the API as the message's error. Here is each one, what it means and how to fix it. Notes (things we accept but our team checks) are at the end.

The message could not be read

The XML file is not valid: ... (line N).

The file is not well formed XML. Open it at that line: usually an unescaped &, a missing closing tag, or a file cut short during upload. Run it through /validate after fixing.

The XML file has a DOCTYPE, which is not allowed in an ERN message.

Remove the <!DOCTYPE> line. ERN messages use XML Schema, not a DTD.

The XML file is bigger than 30 MB.

Split it: one release per message.

This is a ..., not a NewReleaseMessage.

We read NewReleaseMessage and PurgeReleaseMessage. Other DDEX messages (catalogue lists, sales reports) are not read; leave them out of the batch.

The message has no main release (an album, EP or single) in its ReleaseList.

The ReleaseList has no Release. Add the album, EP or single itself (not only track releases). With several, mark the main one with IsMainRelease="true".

This PurgeReleaseMessage does not say which release to remove.

Give the release's ICPN (or the GRid or proprietary id you first sent it with).

The deal

The message has no deal, so there is no permission to stream this release.

Add a ReleaseDeal for the main release with UseType OnDemandStream and CommercialModelType SubscriptionModel and/or AdvertisementSupportedModel.

The deal does not allow streaming this release.

The deal is there but only for other uses (for example downloads under PayAsYouGoModel). Add the streaming use and models above. If a release already on the site comes again without a streaming deal, it is taken down.

The deal takes down every track, so there is nothing left to stream.

Every track release has a TakeDown. To remove the whole release, put the TakeDown on the release deal or send a PurgeReleaseMessage.

The release and its files

The release has no title. / The release has no audio tracks.

Give the main release a DisplayTitleText, and list its sound recordings in its ResourceGroup.

This is a VideoSingle (or another video or ringtone type).

We only take audio releases.

These files are missing from the delivery: ...

The message points to files that are not in the batch. Check that each URI is relative to the message and spelled exactly as the file, case included. Over SFTP we wait up to two hours for late files before giving up.

The audio of N tracks could not be used: ...

The file was empty, not audio, in a format we do not take, or its MD5 did not match the HashSum (acknowledged as ResourceCorrupt). Send the file again.

Reading this message stopped the job N times, so it was given up.

Something in the message broke our reader. Send it to /validate, then contact us with the delivery id if it passes there.

The message changed nothing

This message did not change anything on the site because it was addressed to ..., not to this site.

The MessageRecipient/PartyId is not our DPID. Correct it, or ask us to check the DPID we have for the site.

... because it was sent by ..., not by ...

The MessageSender/PartyId does not match the DPID on your account. Tell us your correct DPID.

... because the distributor marked it as a test message.

A TestMessage never changes a live release. Send it as a LiveMessage.

This message was sent on ..., before the last one applied to this release, so it changed nothing.

Messages arrived out of order. The newer one already applied. Send a new message with a later MessageCreatedDateTime if you meant this one.

API errors

401: Send your API key as "Authorization: Bearer lbxf_..."

The key is missing or wrong. Keys are shown once; ask us for a new one if you lost it.

403: Deliveries from ... are paused on this site.

Your account is paused. Contact us.

422 on /deliveries: .xyz files are not taken / is listed twice / needs at least one ERN message

Send only xml, wav, flac, aif, aiff, mp3, jpg, jpeg and png files, each path once, and at least one message. Paths are relative, without ...

422 on /complete: Not every file arrived complete.

Upload the files in missing and wrong_size again (get fresh links with /links if needed), then call complete again.

409: This delivery is already complete.

Start a new delivery to send more files.

Notes our team checks

• No genre here matches ...: we map your genre to one of ours once, and it is remembered for your next deliveries.
• The deal covers N countries, not the whole world: the site streams worldwide, so a person checks the release first.
• No front cover image / the cover file is missing: send the cover; a release without one cannot go live.
• No AI tool is named: tell us the AI tool your catalogue is made with so it is set on your account.