Free tenant ha-vik: application entity count stuck after delete (too_many_entities)

Get Help
1

POST https://[[tenant_domain]].eu.auth0.com/api/v2/clients returns 403
errorCode: too_many_entities
message: You reached the limit of entities of this type for this tenant.

The dashboard shows the banner “This tenant reached its available applications and SSO integrations limit” and Create Application is disabled.

GET /api/v2/clients?per_page=50&include_totals=true returns total 10.
One of those is the global client “All Applications”.
The other 9 are the only applications listed in the dashboard.
SSO Integrations is empty.

A sibling tenant, ha-khc, shows 10 applications in the dashboard and the same banner, so “All Applications” does not consume a slot. ha-vik has 9 real applications and should have one free slot. Both the dashboard and the Management API still reject creation.

We deleted one application. It no longer appears in GET /api/v2/clients. The entity counter has not decreased.

Please reset the application entity count for ha-vik so we can create one SPA.

3

Hi @anaisabel.dehoz

Welcome to the Auth0 Community!

You are asking Auth0 to reset the application entity count for the Free tenant ha-vik (EU region) so that you can create one Single-Page Application, because the tenant returns a too_many_entities error on application creation even though the dashboard lists nine applications and one deleted application has not lowered the count.

[Summary]

Free tenants allow a maximum of 10 applications, and a change to the tenant entity counter must be verified and made by Auth0 Support, so open a Support case with the evidence listed below.

[Root Cause]

Auth0 enforces entity limits (such as the 10-application cap on Free plans) using an internal counting service.

  1. Cached / Log-based Counters: Entity usage is tracked in a cached entityCounts collection populated via tenant management API log streams (sapi). It does not run a live database count on every POST /api/v2/clients call.

  2. Counter Desynchronization: When an application is deleted, asynchronous cleanup workers or dropped log events can occasionally fail to decrement the stored counter. When this happens:

    • The actual database holds 9 clients (excluding the global “All Applications” client, which does not count toward the quota).

    • The stored entity counter remains at 10.

    • Both the dashboard and the Management API consult the stored counter and reject new creations with 403 Forbidden (too_many_entities).

[Solution]

Because this is a desynchronization in Auth0’s backend data store, only Auth0 support or platform operations can force a recount.

  1. Submit a Request to Auth0:

    • Paid / Assisted Support: If you have an organization account with support entitlement, open a support ticket via the [Auth0 Support Center] (https://support.auth0.com/).

    • Free Tier: If you only have community access, send a DM to the @support group in the [Auth0 Community Forum] (https://community.auth0.com/)

  2. Information to Include:

    • **Tenant Name / Canonical Domain

    • **Email address of your Auth0 account

    • Error: 403 Forbidden / too_many_entities on POST /api/v2/clients

    • Actual count vs stored count: Mention that GET /api/v2/clients returns 10 total clients (1 global client + 9 active clients), but creation is blocked due to a stale entity counter after an application deletion.

    • Action requested: Request an entity limit count reset / recount for clients on tenant the tenant.

[Immediate Workarounds]

  • Repurpose an existing client: If one of the remaining 9 applications is a test, inactive, or placeholder client, you can reconfigure it instead of creating a new one:

    • In the Auth0 Dashboard, open the application → Settings.

    • Update Application Type to Single Page Application.

    • Update the Application Name, Allowed Callback URLs, Allowed Web Origins, and Allowed Logout URLs.

    • Use the existing client_id for your SPA.

  • Temporary Development Tenant: Create a temporary secondary tenant to continue testing your SPA while support clears the counter.

Kind Regards,
Nik