Release History provides a chronological overview of the important actions and changes connected to a release. It helps administrators and artists understand what happened, when it happened and which stage the release has reached.

What Release History Records

Depending on the available Artist OS features and permissions, the release timeline may include:

  • The date and time the release was created.
  • Changes to titles, credits, metadata or release dates.
  • Artwork or audio replacements.
  • Status changes such as Draft, Processing, Distributed or Live.
  • Validation warnings, corrections and resubmissions.
  • Distribution-related actions and important administrative notes.

Opening the Release History

  1. Open Release Management.
  2. Select the release you want to review.
  3. Open the release details page.
  4. Select History, Activity or the equivalent timeline option when available.

Reading the Timeline

History entries are normally shown from newest to oldest. Each entry should identify the action, the date and the current result. Review the surrounding entries when you need to understand why a release changed status or why a correction was required.

Typical Timeline Events

  • Release created: the first draft was saved.
  • Metadata updated: one or more release fields were changed.
  • Files replaced: artwork or audio was uploaded again.
  • Submitted: the release entered the distribution workflow.
  • Validation failed: an issue requires attention.
  • Distributed or live: the release completed an important publication stage.

Why Release History Matters

A clear history is useful when several people work on the same catalogue, when a release needs troubleshooting or when you must verify which information was active at a particular moment. It also reduces confusion by keeping important actions attached to the release itself.

Best Practices

  • Review the history before making another major change.
  • Use clear internal notes when Artist OS provides a notes field.
  • Avoid unnecessary repeated edits shortly before distribution.
  • Confirm that requested corrections appear in the timeline.
  • Keep external approvals or important correspondence in your project records when they are not stored directly in Artist OS.

Troubleshooting

If an expected event does not appear, refresh the page and confirm that the action was successfully saved. Also check your permissions, because some history details may only be visible to administrators or authorised partners.

  • Release Status
  • Updating Existing Releases
  • Distribution Process
  • Release Scheduling