Not necessarily. This could just be a side effect of cacheing.

Basically, the airlines have learned expensive lesson that showing true availibility for redemption bookings is costly, because of the very large numbers of searches people do. True availability requires a call back to the revenue management system, taking into account POS/POC/frequent flyer tier/ currency/ current demand/ supply balance etc etc

So rather than show each other the true availability on search, you use a cache, and only update the cache when required. But there is then a risk that the cache and reality are out of sync, and when pax actually makes booking, so sorry, not available.

The way to reduce this risk is to be conservative on what the cache shows. So even if CX has 6 seats, you tell your partners you only have 1. And you only need to update the cache when you go to 0, (or more seats opened up) rather than updating the cache from 6 to 4 back up to 5 etc.