Hi AJ,

I'm not sure I completely understand. A simple example for Suicide Squad:

https://api.themoviedb.org/3/movie/297761?api_key=###
https://api.themoviedb.org/3/movie/297761/videos?api_key=###

Better yet, lets do this all in a single query:

https://api.themoviedb.org/3/movie/297761?api_key=###&append_to_response=videos

it's happened a few times over the last few months. i have 2 different systems, one does the basic info, the other does the videos. given your 2 URLs example.. i was getting data for the first one, and a 404 for the second url. which leads me to believe they are somehow out of sync. i re-did the offending film id the following day and the issue cleared.

it's happened again, just now.. http://api.themoviedb.org/3/movie/309487/videos is returning 404. yet http://api.themoviedb.org/3/movie/309487 is not. also id: 335389

So this movie was deleted which would explain the behaviour you're seeing. The cached result was still being returned because it was requested (and therefore cached) when it was still here. But the videos call wasn't cached and therefore 404'd instantly.

Now that the cached item has been purged, both requests 404.

ok, so a 404 on either should be considered a 404 for both; and i should presume its a cache issue? do you have any idea how long these cache expiry is set for?

These items are cached for 6 hours.