I think what happened here is the result of the previous bug that appeared when migrating to #237 which was investigated and fixed here
We fixed the case when someone is going from the current production to the EA build which contained the fix, however, it was hard to fix a migration from broken state #237 → #243 and that’s why you are seeing this. So, probably, moving playlists around is a valid workaround for this now 
Apologies for troubles.
–
Ivan