Handle a catalogue incident without losing the audit trail
Handle a catalogue incident with a factual case record, controlled changes and verified communication. Preserve the evidence needed to understand what happened before deleting files or changing accepted allocations.
Record the incident
Identify affected products, recordings, accounts, destination links and observed times. Distinguish a confirmed problem from an unverified report. Keep screenshots and original notices privately, with unnecessary personal information removed from working summaries.
Establish authority and scope
Name the authorised case owner and which actions they can approve. Account security, metadata correction, rights complaints and payout issues can require different routes. Do not assume authority over another owner’s catalogue merely because an incoming split is affected.
Control changes
Document each proposed action, approval, previous value and verification plan. Contact the relevant authorised provider through its supported route. Avoid competing resubmissions or financial changes made to compensate for an unexplained incident.
Verify and learn
Record the actual outcome, unresolved issues and prevention task. Preserve source reports and change history. This guide does not establish regulatory incident deadlines or certify a security response; seek appropriate specialist review for the actual case.
Sources and scope
Reviewed 4 November 2026. Source prices retain their listed currency. No production account, provider API, payment, invitation or publication is connected. Confirm current account and agreement terms before acting.