Skip to main content

Error Descriptions in Job Status Responses

When polling the job status endpoint, any errors encountered during processing will be included in the StatusResponse. Additionally, these error descriptions are also provided in the Status information sent with webhooks, offering insight into why a job may have failed. Below is a list of possible errors and their descriptions:

  • Audio file format could not be parsed!
    This error occurs when the file format is not supported by our API. Please check the File Formats Page page for details on supported formats.

  • Audio file must be longer than 5 seconds!
    Files shorter than 5 seconds cannot be analyzed for musical context. Please provide a file with a longer duration.

  • No notes found!
    This error can happen with audio files containing no sound, highly distorted audio, or excessive background noise.

  • No beats found!
    Particularly relevant for beat-tracking tasks, this error may occur if the audio is a-rhythmic, has a tempo outside the 40-300 bpm range, or suffers from quality issues similar to those described in "No notes found!"

  • Unknown error!
    For unexpected issues, an internal alert is sent to our development team, who will take immediate action to resolve the problem.

Example JSON Response with an Error​

Below is an example of a JSON response body for a job that has failed:

{
  "status": "FAILED",
  "error": "Audio file format could not be parsed!"
}