Some songs in specific queries are delivered on two different pages as search results. An example would be the song "Starlight" here:
Interestingly, this happens for the query "muse" on both production and dev, even though they use different databases. So far, it seems to only happen for the query "muse", other queries delivering multiple pages of results do not have this issue. It is also exactly the same song being delivered by the backend (same song ID for both songs), this is not a frontend issue.
It also happens on some other query, e.g. "Katy" or "Taylor". It's always only a single song being a duplicate. This does not always happen on the second page, it can also occur between the first and third page e.g.
Some songs in specific queries are delivered on two different pages as search results. An example would be the song "Starlight" here:
Interestingly, this happens for the query "muse" on both production and dev, even though they use different databases. So far, it seems to only happen for the query "muse", other queries delivering multiple pages of results do not have this issue. It is also exactly the same song being delivered by the backend (same song ID for both songs), this is not a frontend issue.