It might be that someone searched for that ID before the cache server cached it. Wait for 24 hours when the cache is flushed, I think its 24 hours.

Dale.

Hi johnb003,

The current id 208983 (as of 8:19 AM MST this morning) seems to be returning data:

http://api.themoviedb.org/3/movie/208983?api_key=###

Do you have another example?

It is indeed like what Dale said though. 404 pages are not supposed to be cached but there is clearly a bug lurking around there somewhere that is causing them to be.

So here's what I get from my python shell, note the id returned, and passed in.

>>> pprint.pprint(json.loads(requests.get('https://api.themoviedb.org/3/movie/latest?api_key=###').content))
 {u'adult': False,
  u'backdrop_path': None,
  u'belongs_to_collection': None,
  u'budget': 0,
  u'genres': [{u'id': 99, u'name': u'Documentary'}],
  u'homepage': u'',
  u'id': 209100,
  u'imdb_id': u'tt2197934',
  u'original_title': u'In Bed with Ulysses',
  u'overview': u"How the novel that is widely considered the greatest work of modern fiction was created and the toll it took on James Joyce's family.",
  u'popularity': 0.0,
  u'poster_path': u'/erJkUYKqiBcFqRfABG1QB0N8ZjT.jpg',
  u'production_companies': [],
  u'production_countries': [],
  u'release_date': u'2012-06-11',
  u'revenue': 0,
  u'runtime': 80,
  u'spoken_languages': [],
  u'status': u'Released',
  u'tagline': u'',
  u'title': u'In Bed with Ulysses',
  u'vote_average': 0.0,
  u'vote_count': 0}

pprint.pprint(json.loads(requests.get('https://api.themoviedb.org/3/movie/209100?api_key=###').content)) {u'status_code': 6, u'status_message': u'Invalid id - The pre-requisite id is invalid or not found'}

Yea I have checked the API still needs some time to clear it's cache. Travis might be able to help it alone.

Dale/

Clearing the cache seems like a short term solution. Perhaps ids > latest can be prevented from caching at all.

Perhaps ids > latest can be prevented from caching at all.

That's how it's supposed to work but like I mention above, there's a bug in there somewhere that isn't actually working.

Hi, the issue is still open.

this call doesn't work. http://api.themoviedb.org/3/movie/4258?api_key=APY_KEY

{"statuscode":6,"statusmessage":"Invalid id - The pre-requisite id is invalid or not found"}

this call work: http://api.themoviedb.org/3/movie/04258?api_key=APY_KEY

the ID field must be not less 5 numbers now?

With regards to Scary Movie 5 (4258), please see this thread: https://www.themoviedb.org/talk/51f811c819c2953a8928df8c

Ah ok. Thanks for the quickly reply. Regards

Travis, any update on this caching bug? It still appears to be an issue; I’m fielding queries from our members frustrated that new films they add to TMDb aren’t immediately available for import via the API, as they used to be under 2.1.

Hey guys,

I've created a new ticket for this here. I'm in the middle of some feature work that needs to get done and I don't imagine finding time to look at anything else until it's completed in ~2 weeks. I'll make sure to take a look at it then.

Cheers.

Thanks Travis.

The fix for this was just pushed live. Already cached items won't show any difference but as they expire, no new invalid ids should be cached.

Had to revert it for the time being, I will work on this next week.

Oh no! I feel your pain, Travis. Caching is a harsh mistress. I wish you luck!