OK,
so should I understand that https://www.ventismedia.com/mantis/view.php?id=17000 is still fixed correctly,
i.e. HTTP 429 error, which means "API rate limit exceeded". is seen just in the deug log and MediaMonkey waits and re-tries, so the whole sync progress task takes just longer?

tested fix in 2270, all working well on a large number of playlists. This is a great feature!
Thanks
Alan

Thanks Ludek, yes I'm certainly a power user for that feature
will monitor

Thanks, in the debug log I see that the HTTP error 429 is "API rate limit exceeded"

There were thousands of tracks to match and the Spotify API is somehow limited with the amount of requests.
Tracking this issue as https://www.ventismedia.com/mantis/view.php?id=17000

sure, all done, PM should be with you

Could you please generate debug log (item 4b here https://www.mediamonkey.com/forum/viewt ... 30&t=86643 ) and share it via private message with me?

Got back to beta testing MM5 (I was interested in GPM sync but stopped testing since GPM is shelved), hopefully Spotify can replace what I wanted to do:
Now Running 2269, I have about 61 playlists that I'm syncing to Spotify premium account. The playlists don't all sync over, first 75% sync fine but the remainder never copy over at all. It has the following symptoms:

1) Matching section works fine (with expected match errors)
2) about 75% through the syncing of the playlists it seems to hit issues and jumps to the end
3) it completes the sync with the expected "problem synchronizing the following item(s):
4) Match errors first, all good and expected, then the report first highlights "Spoitfy:_addTracks2Playlist error: 429
5) The all subsequent playlists have an entry marked "getUserInfo error: 429 reported until end

The playlist that causes the failure is not the same every time.