Skip to main content

Analyze Library Tracks

The analysis of a library track with all the available classifiers will automatically be started upon creation.

However, in case the analysis limit for a time period has already been reached, the analysis will not be enqueued and must be manually enqueued at a later point (when the limit got reset/increased) using the Mutation.libraryTrackEnqueue field.

The Mutation.libraryTrackEnqueue returns the LibraryTrackEnqueueResult GraphQL union type which can either be LibraryTrackEnqueueSuccess or LibraryTrackEnqueueError.

Enqueue succeeded​

In case the Mutation.libraryTrackEnqueue result is LibraryTrackEnqueueSuccess, the library track got successfully enqueued.

Enqueue failure​

In case the Mutation.libraryTrackEnqueue result is LibraryTrackEnqueueError, the library track could not be enqueued. The error and message field on the LibraryTrackEnqueueError contain a detailed description on why the library track could not be enqueued.

Error code overview​

Error codeMeaning
limitExceededThe analysis limit was exceeded.
libraryTrackNotFoundThe LibraryTrack with the provided id does not exist.
rateLimitExceededThe rate limit for enqueuing a LibraryTrack has been exceeded.

Next steps​

A detailed overview can be found on the GraphQL schema documentation: