Announcements

Help Wizard

Step 1

NEXT STEP

FAQs

Please see below the most popular frequently asked questions.

Loading article...

Loading faqs...

VIEW ALL

Ongoing Issues

Please see below the current ongoing issues which are under investigation.

Loading issue...

Loading ongoing issues...

VIEW ALL

Who Me Too'd this topic

Getting saved tracks returns inconsistent result for different offsets

Plan

Premium

Country

GB

 

Device

It's dev API

Operating System

N/A

 

My Question or Issue

Last 2-3 days I started observing a strange behaviour - I'm requesting all the saved tracks for a user and for some of requests the API returns an empty result even though there ARE tracks in the range.

 

For example, this is logs from my app:

 

 

Response: href=https://api.spotify.com/v1/me/tracks?offset=200&limit=50, limit=50, next=null, offset=200, previous=https://api.spotify.com/v1/me/tracks?offset=150&limit=50, total=0, items.length=0

Response: href=https://api.spotify.com/v1/me/tracks?offset=250&limit=50, limit=50, next=https://api.spotify.com/v1/me/tracks?offset=300&limit=50, offset=250, previous=https://api.spotify.com/v1/me/tracks?offset=200&limit=50, total=2272, items.length=50

 

 

 

Note here that the second response that has higher offset (250) has some tracks, but the previous request doesn't have any tracks and even its `total` field is empty.

 

Can you fix the API please? It's really annoying getting such gliches due wrong deploy and fix the app time to time although nothing has changed, and as soon as the issue still persist after a few days you aren't even noticed about that by your metrics or alerts.

Who Me Too'd this topic