I've confirmed this for several titles in my queue, and many of my customers are complaining about it. I've confirmed that I'm displaying exactly what the Netflix API sends for title availability (see http://api.netflix.com/categories/queue_availability for enumeration of values), but that these do not match what is reported in my queue on Netflix.com.
This leads customers to think my application is buggy and unreliable.
Thanks! Glad to know it's being looked at. I notice the fact that deleting a title generates but does not return a new etag is not listed in the known issues.
I've confirmed this for several titles in my queue, and many of my customers are complaining about it. I've confirmed that I'm displaying exactly what the Netflix API sends for title availability (see http://api.netflix.com/categories/queue_availability for enumeration of values), but that these do not match what is reported in my queue on Netflix.com.
This leads customers to think my application is buggy and unreliable.
Message edited by Brent 3 years ago
mikey – 3 years ago
Hey Brent, can you give us some examples?
Thanks!!
=-mike-=
Brent – 3 years ago
Yeah. The only one in my queue right now is "Jumper" (shows "Now" through API, "Short Wait" on netflix.com).
mikey – 3 years ago
we are looking into this, and will let you know when it is fixed..
John Haren – 3 years ago
@Brent: We've also added a Known Issues page where you can check the status of reported items. It's at http://developer.netflix.com/Known_Issues.
Brent – 3 years ago
Thanks! Glad to know it's being looked at. I notice the fact that deleting a title generates but does not return a new etag is not listed in the known issues.