It continues, now the 1brs are impacted too, here the 13th, 14th and 15th are gone already. However the 10th,11th and 12th is still there.
View attachment 548940
View attachment 548941
Throwing out some guesses... just because it's fun to pontificate on this subject
If I had to bet on it, I would say this is either due to a system bug or a poorly designed points reservation engine (which might be the same thing depending on your definition of a system bug)
From our standpoint we'd assume the reservation engine would look at all currently available rooms in real-time and let you grab what's available on a first-come basis. I'm guessing the system has evolved over the years (like many IT systems) and there may be some data inputs that aren't real time causing some undesirable results when inventory gets low.
For instance, maybe the future available inventory calendar is "generated" every night - with assumptions made on what days are more likely to have 1 BR's / studios booked vs 2Br's... and maybe in the case above, there are more 2 BR's "allocated" in DVC's calendar than 1 BR's / Studios for the 10th, 11th, 12th. Normally not an issue within the 11 month mark, but causes problems in the 11month +7 day timeframe where users can only book one type of room for all 7 days.
Either that, or DVC has the ability to book 11 month +7 days on a non-contiguous basis (i.e. they can book/hold some weekend days in the 11 month +7 days timeframe without having to book a contiguous block) - possibly a "loophole" in the booking requirements differentiating what DVC members vs DVC themselves can reserve (or take out of inventory)..... but if I had to bet on it I'd say it's due to a bug, or more likely a nuance of a booking engine that has some accuracy issues due to the way it was originally designed and now ported to a real-time web interface booking tool.
... and if my guess is right, based on my experience in IT, it will be a while before this is addressed (unless they've already been working on it for a while). Stuff like this usually requires a significant change to core elements of the system (database/datastore), which then requires changes to the interfaces, and then a ton a testing to make sure everything still works (especially if it's a legacy system at its core). Basically, lots of time and money. I wouldn't doubt there are product and technical people who have raised the issue internally and suggested fixes - but then someone asks what's the ROI, and I bet the numbers probably don't look convincing so it's gets put on the todo list until there's enough other income generating enhancements to justify a large project.
I'm also guessing DVC is probably not going to say "hey, our booking systems has some deficiencies but it's good enough and really not worth it to fix the problem right now". It will be interesting to see what they respond with. I'm guessing it will be a vague response.
Lot's of guessing...
Very interesting topic... thanks for documenting this and following up with Disney.