[Bug]: The account limit of this instance has been reached, but only 63/100 active users

⚠️ This issue respects the following points: ⚠️

• This is a bug, not a question or a configuration/webserver/proxy issue.
• This issue is not already reported on Github OR Nextcloud Community Forum (I've searched it).
• Nextcloud Server is up to date. See Maintenance and Release Schedule for supported versions.
• I agree to follow Nextcloud's Code of Conduct.

Bug description

We use nextcloud aio and use the ldap sync which worked for months, but since a few days we are getting the error Das Kontenlimit dieser Instanz ist erreicht. If I go to Settings -> Konten: Alle Konten only lists 7 Accounts, so way less then 100. If I go to Deaktivierte Konten 325 Accounts are listed, but they are there since day one months ago and back then this also was not a problem and https://github.com/nextcloud/server/blob/01b2ae4e4e47a58e3036184bbd52d8fdd76ee412/lib/private/Support/Subscription/Registry.php#L189 indicates that disabled users do not count.
I also opened a discussion at the aio repo but they said I should create a bug report here (https://github.com/nextcloud/all-in-one/discussions/5655).

Steps to reproduce

1. Use Nextcloud AIO
2. Use the LDAP Sync with more than 100 users but disable most of them (??)
3. Wait some months (??) and get the error that you have to many users.

Expected behavior

Don't get the error that I have more than 100 users or list more than 100 users in the Active Users list.

Nextcloud Server version

30

Operating system

Debian/Ubuntu

PHP engine version

PHP 8.3

Web server

Nginx

Database engine version

PostgreSQL

What user-backends are you using?

• Default user-backend (database)
• LDAP/ Active Directory
• SSO - SAML
• Other

Configuration report

Nice way to get this from aio? Would be nice if I could just download this from the admin settings

Start with lib/private/Support/Subscription/Registry.php around line 189, which the report identifies as the account-counting logic. Trace how LDAP synchronization and disabled users contribute to the active-user limit, then inspect the related account-limit entry points. Done means reproducing the mismatch and ensuring the reported limit reflects active users rather than excluded disabled accounts.