Custom sort not respected

[G4Zz0L1]

Why in the custom collections taken from the default templates of the repository, the collection_order custom is not respected at each update?
The only difference I have from the git is only the collection_mode value set to hide on everything, to not show them in the library (and there's an issue already opened for this, the separators ignores the collection_mode hide).
I would like to open an issue, but in the logs there are no errors, in the sorting section (after adding and missing sections) it correctly writes all the videos as they should be.
Yet the result is not what it says in the logs, it seems as if some videos are always put at the beginning before the others.
It only happens in subsequent runs, if I delete a collection in the next run it will be sorted correctly.
Then the next time, it screw things up again.
Do you have any ideas?

[G4Zz0L1]

I'll add that nothing on this github works so far, everything points to the fact that I've to finish the run, but the problem it's not in the current run, but in the ones after the first.
There are other discussions and issues on this marked as solved, but they don't apply to this specific thing.
Am I the only one with this problem?

[TheChrisK]

Yeah I am noticing that as well. I created a Western collection based on an imdb list and when it finished, three movies that are in that collection and the IMDb Top 250 ended up being moved to the top in the 250 list.

[G4Zz0L1]

We'll wait for some news from the devs, I suspect there's a bug or misconfiguration somewhere, but I don't know if it's in PMM or Plex.

[chazlarson]

FWIW, with a larger library [9000 movies] I now see this behavior. It really seems like it's on Plex' side, since PMM is doing the correct thing according to the log. It appears that there are still some issues in Plex around setting custom orders using the same movies between different collections.

[G4Zz0L1]

I haven't found anything useful online, and if it's on plex I don't think we can fix this here.
But what can we do to avoid this? We just have to wait for them to fix this?
It really pisses me off that on the collections where it matters the order isn't right.

[rbraunschweig]

This was less problematic when sorts were performed at the end of a run. A config option for sorting after each collection or library run could work for now.