Server - Emby to take action on known bad response from TMDB and update itself

[ginjaninja 536]

eg. http://api.themoviedb.org/3/person/1469590?api_key=f6bd687ffa63cd282b6ff2c6877f2669&append_to_response=credits,images,external_ids

 

At some point TMDB changed the person id related to this and this one is no longer valid (but the id is stored in person.xml from a previous once successful lookup)

On manual refresh or schedule person refresh task, Emby does nothing with the TMDB response...

"{"status_code":34,"status_message":"The resource you requested could not be found."}"

 

Presumably this is a different response to http error 404 or TMDB service offline so there is no chance for false positives.

 

If Emby knows its TMDB data is out of date, it would be better if emby tried to re-search/re-acquire the correct data from first principles rather than continue to accept a known bad position ad-infinitum. (when the metadata is not locked)

 

 

 

[Luke 37069]

Yup