Hi @alexguz79,

Yes, this is a known issue. If you look at the dates being returned, they will flip back and forth between two date ranges which is what is causing the different pagination data. This is on my list to fix.

Thanks for the response Travis.

Great Help.

FYI, I've been playing with trying to get this bug fixed and it's been a tricky one to track down. I am not currently, seeing it but can you tell me if you do?

Thanks Travis

i had to create a workaround back in December and it's working for me.

Here's what i did:

First thing i do is truncate the table with coming_soon ids, then I run the query 3 times https://api.themoviedb.org/3/movie/upcoming?api_key=###&language=en-US&region=US ( since i noticed one of those queries will have the total count ), store each id when id is not already in DB and finally use those ids to display the info on each one.

It takes a little longer but was the best solution at the moment.

I'll re visit my code and see if the issue persist, in any case i will update.

Thanks again.

Ya, some work has been done to try and make sure the same data range is always returned. Like I mentioned, it's been annoying to fix because it never did happen on my dev environment, only ever production (for reasons I don't understand).