Access Schedules Are Community-Keys-Only
What changed: keySchedules() returns the community’s own key(s) only, and keySchedule() / setKeySchedule() reject a member’s key with a 403 carrying code: "not_a_community_key". A community manager is not permitted to change a member’s individual schedule; the community-wide rule already covers every member.
Where to find it: client.community.keySchedules(), .keySchedule(), .setKeySchedule()
What you’ll see: A shorter list. descendantKeyCount counts live member keys only, and a new inactiveWindowCount reports windows the list filtered out as expired.
What you need to do: Schedule the community key rather than a member’s key. Nothing you could legitimately do is lost.
Who this affects: Customers using the npm SDK