TikTok reached_active_user_cap: why disconnecting and reconnecting won’t fix it
TikTok's reached_active_user_cap is an app-level quota on unaudited clients, not a per-account problem. Here's what actually raises the cap.
By André Lugreached_active_user_cap means your unaudited TikTok developer app hit its own limit on distinct authorized accounts — TikTok's guidelines allow unaudited clients up to 5 users posting in a 24-hour window. The cap belongs to your app, not the user, so disconnecting and reconnecting never helps. Passing audit is the primary fix; TikTok can also raise the cap on request.
A new customer tries to connect their TikTok account and the OAuth flow comes back with reached_active_user_cap. Your first instinct is to have them disconnect and reconnect, or to have them try from a different browser, or to check whether their TikTok account itself has some restriction. None of that will work, because the cap this error refers to belongs to your app, not to the user trying to connect.
PostGate handles OAuth, publishing and delivery evidence for every network through one API. Start free or read the docs.
What actually is the cap?
While a TikTok developer app is unaudited, TikTok limits how many distinct real TikTok accounts can authorize and use it. Per TikTok's own Content Sharing Guidelines: "Unaudited API Clients can allow up to 5 users to post in a 24 hour window." That documented figure is a rolling window, not a one-time lifetime allowance — and it is separate from rate limiting and separate from the private-only-posting restriction unaudited apps also face.
TikTok's developer FAQ confirms the cap is a real, app-level quota you can ask TikTok to raise ("Please contact us via our Support form to request an increase in your active user cap"), but it does not spell out the exact mechanics of how the window rotates users in and out. Developer reports generally describe it resetting on a roughly 24-hour cycle rather than staying permanently exhausted, but TikTok does not commit to that behavior in writing — and the exact number and window can change as TikTok updates its developer program, so check the cap for your own app in the TikTok developer portal rather than assuming a number from someone else's experience.
Why doesn’t disconnecting and reconnecting help?
The cap counts distinct authorized accounts against your client key, not your app's active concurrent sessions. Disconnecting a user in your own database does not tell TikTok anything — TikTok is the one tracking who has authorized your app, not you — so reconnecting the same user is not what frees up room, and a genuinely new TikTok account attempting to authorize while you are at the cap will still be rejected even if plenty of your existing connections are idle or disconnected on your side.
This is the detail that causes the most confusion: your product might show plenty of "available" slots because customers disconnected weeks ago, while the cap TikTok is actually enforcing has nothing to do with what your database currently shows as connected. If the cap does roll off after roughly 24 hours as commonly reported, waiting it out can free up room for a new authorization — but there is no self-service action on your end (no disconnect, no reconnect, no retry) that changes the outcome any faster than that.
What actually raises the cap?
- Passing audit. This is the primary path. Audited apps operate under materially higher limits than unaudited ones, and for most production TikTok integrations this is the only sustainable fix.
- Requesting a limit increase through TikTok directly, where that option is available for your app's category — this is not guaranteed and is not a substitute for audit.
- Nothing you can do from your own infrastructure. There is no API call, dashboard toggle, or support workaround inside your own stack that increases this number. It is enforced entirely on TikTok's side, keyed to your app's audit status.
How do you build around it before audit completes?
Until your app is audited, plan your rollout around the cap rather than discovering it in production. Track how many distinct TikTok accounts are authorizing your client key within a given window, since that — not how many connections your own database currently shows as active — is the number TikTok is actually enforcing against. If you are running a closed beta, gate new TikTok connections deliberately so you do not burn through your window's allotted cap on internal testing and demo accounts right before your first real customers try to connect.
It is also worth telling customers plainly what is happening when this error fires — "TikTok connections are temporarily limited while our app completes platform review" is accurate and sets the right expectation, versus a generic connection-failed message that makes the problem look like it is on their end.
How does PostGate surface this?
A rejected TikTok authorization due to the active-user cap fails at the connection step, before any post is ever attempted, so it will not show up as a delivery failure in PostGate's per-target logs — it shows up as a failed connect attempt. PostGate's structured error envelope carries the platform-level reason through instead of collapsing it into a generic "connection failed" message, so you can message the customer with the real cause instead of asking them to retry a step that cannot succeed.
Frequently asked questions
Why doesn't disconnecting and reconnecting fix reached_active_user_cap?
Because the cap counts distinct TikTok accounts that have authorized your client key — TikTok tracks that, not you. Disconnecting a user in your own database tells TikTok nothing, so it doesn't free up room, and a genuinely new TikTok account will still be rejected at the cap even if plenty of your existing connections look idle or disconnected on your side.
Does the TikTok active user cap reset over time?
Developer reports generally describe it resetting on a roughly 24-hour rolling cycle rather than staying permanently exhausted, but TikTok does not commit to that behavior in writing. If it does roll off, waiting can free room for a new authorization — but no self-service action on your end (disconnect, reconnect, retry) changes the outcome any faster.
What actually raises the active user cap?
Passing TikTok's audit is the primary path — audited apps operate under materially higher limits, and for most production integrations it is the only sustainable fix. TikTok's developer FAQ also says you can request an increase via its Support form, though that is not guaranteed and not a substitute for audit. Nothing inside your own infrastructure — no API call, dashboard toggle, or workaround — increases the number.
How should I run a beta while my TikTok app is still capped?
Track how many distinct TikTok accounts authorize your client key within a given window — that is the number TikTok enforces, not what your database shows as connected. Gate new TikTok connections deliberately in a closed beta so internal testing and demo accounts don't burn the window's allotment right before real customers connect, and tell customers plainly that TikTok connections are temporarily limited while the app completes platform review.
