Access Schedules Are Community-Keys-Only
What changed: key_schedules() returns the community’s own key(s) only, and key_schedule() / set_key_schedule() raise PermissionDeniedError (not_a_community_key) for a member’s 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.key_schedules(), .key_schedule(), .set_key_schedule()
What you’ll see: A shorter list. descendant_key_count counts live member keys only, and a new inactive_window_count 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 Python SDK