DISTROBOLT ARTIST GUIDES
Respond to a metadata rejection with a corrected draft
Work from the exact rejection reason to a controlled correction. A revised draft should show what changed and why, rather than replacing several unrelated fields and hoping the next review accepts it.
Preserve the notice
Save the rejection message, release reference, destination where identified and the version submitted. Classify the issue as metadata, artwork, audio, rights evidence or another stated reason. If the message is unclear, ask DistroBolt which field or file needs attention before editing. Do not turn a reviewer’s suggestion into an invented universal rule.
Prepare a correction record
Use four fields: rejected value, stated reason, proposed replacement and approval owner. Example: for a misspelled guest name, confirm the approved spelling and profile before changing the contributor entry. For the wrong artwork, supply the correct export. Keep unrelated approved metadata stable so that the revision can be compared reliably.
Check whether a normal correction is possible
Some destination decisions require clarification rather than an ordinary update. Apple distinguishes editorial hides from fixable delivery tickets, so repeated delivery is not a universal remedy. Ask for the supported route in the actual case. Do not create a new title or artist identity simply to bypass a decision or conceal unresolved rights issues.
Approve and verify the resubmission
Have the relevant artist or authorised release owner review the corrected snapshot. Record who submitted it and retain the case reference. A resubmission is not acceptance and does not guarantee the original launch date. Check the final review outcome, notify the campaign owner if timing changes and archive both the rejection and the approved correction for future releases.
Sources and review
Reviewed 4 November 2026. Platform requirements and plan terms can change. Examples are planning aids, not a promise of account access, release acceptance or earnings.
Continue your release planning
Ask the DistroBolt team about your release. Send a concise question and release reference; never send account passwords or verification codes.