# Known Limits

> Understand a hub limit reached message and check Thalovant plan, connection, runtime, support, and safety limits before changing setup.

Source: https://docs.thalovant.com/help/known-limits/

---
{/* Last Edit: Claude Opus 5.5 - 2026-09-28 - Motive: Home and Work plan limits, Free memory limit, public hub review, media skills, plan-first API errors. */}

Use this page when an action is locked, unavailable, not showing, or behaving like a boundary rather than a setup failure. If the product says can't add, start here before changing setup.

Billing is the source of truth for workspace limits. Service status is the source of truth for broad service incidents. This page helps you separate plan, usage, safety, service-status, and live-status boundaries from real setup problems.

It also covers three boundaries that look like faults: the Free plan remembering only one thing, a public hub waiting for review or missing from the catalogue, and a music or video skill that isn't in the Skill Store.

## Source of Truth

| Limit area | Where to confirm it | What to capture |
| --- | --- | --- |
| Current plan | [Billing and Plans](/workspace/billing-and-plans/) | Plan name and the message beside the locked action. |
| Owned hubs | [Billing and Plans](/workspace/billing-and-plans/) | Current owned hub usage and limit. |
| Connections | [Billing and Plans](/workspace/billing-and-plans/) and [Connections](/concepts/clients/) | Current usage, client state, and whether setup material exists. |
| Private skill setups | [Billing and Plans](/workspace/billing-and-plans/) and [Skill Sets](/concepts/skill-sets/) | Whether the plan includes private skill setups. |
| Runtime config | [Runtime](/concepts/runtime/) | Skill set assignment and runtime setting involved. |
| Skill, runtime, and hub updates | [Manage Updates](/manage/manage-updates/) | Update owner, release target, and whether Billing allows the action. |
| Analytics | [Billing and Plans](/workspace/billing-and-plans/) and [Analytics](/workspace/analytics/) | Whether usage analytics need workspace hub capacity, plus selected range and filters. |
| Hubs created from code | [Billing and Plans](/workspace/billing-and-plans/) and [Provision Hubs](/developers/provisioning/) | Whether the plan allows hub creation, and whether the API token carries the write scope. |
| Personal memory | [Free Tier](/start/free-tier/#one-memory-item) and [Memory](/workspace/memory/) | Whether the account is on Free, which keeps one memory item. |
| Public hub listing | [Billing and Plans](/workspace/billing-and-plans/#publish-a-public-hub) | The hub's review status and how many listings the plan allows. |
| Home or Work line | [Billing and Plans](/workspace/billing-and-plans/#two-plan-lines) | Whether the feature belongs to the Work line only. |
| Live status | [Topology](/concepts/topology/) | Connected, stale, missing, warning, and filter state. |
| Service status | Service status | Current incidents before reporting a broad outage. |
| Account security | [Profile and Security](/account/profile-security/) | Two-step sign-in, recovery codes, and active browser status. |

## Plan and Usage Limits

  
    If Billing shows the owned hub limit has been reached, reduce usage or change plan before creating another owned hub.
  
  
    Connection creation, setup links, and connection file access can be limited by plan, usage, or account security checks.
  
  
    Private skill groups, shared runtime settings, and runtime updates depend on the workspace path shown in Billing.
  
  
    Hub release operations depend on owned hub capacity. Check Billing before treating a locked update button as a product issue.
  
  
    Home and Family get a managed hub address. Custom addresses on your own domain need a Work plan. Check Billing before treating an address message as a setup failure.
  
  
    Free keeps one personal memory item. The second one needs the Home plan, or deleting the first.
  

## Plan Limits at a Glance

| Limit | Free | Home | Family | Workspace | Business |
| --- | --- | --- | --- | --- | --- |
| Owned hubs | 0 | 1 | 2 | 3 | 3 |
| Client connections | 1 | 5 | 12 | 25 | 40 |
| Access rules | 0 | 10 | 10 | 100 | 150 |
| Intents per day | 100 | 300 | 1,000 | 2,500 | 5,000 |
| Personal memory items | 1 | Unlimited | Unlimited | Unlimited | Unlimited |
| Public hub listings | 0 | 0 | 0 | 0 | 1 |
| Autoscaling hubs | 0 | 0 | 0 | 0 | 1 |
| Extra people | 0 | 0 | 1 adult | Unlimited seats | Unlimited seats |

Larger Work plans are compared on [Billing and Plans](/workspace/billing-and-plans/#work-plans).

## Home Line Boundaries

The Home line (Free, Home, and Family) never includes public hub listings, custom hub addresses, invoices, staff invites, autoscaling hubs, or approved browser SDK origins. Family's one extra adult login is the only extra person on the Home line. These are line boundaries, not setup failures: moving to a Work plan is the path when you need them.

## Public Hub Review

Every public hub passes a Thalovant review before it appears in the public catalogue, on every plan. A hub you just made public shows **pending** until the review ends. A **rejected** hub stays unlisted and shows the review note. Your plan also caps how many hubs can be listed at once.

## Skills Not in the Store

Some media skills are not installable from the Skill Store for licensing reasons: YouTube, YouTube Music, Spotify, SoundCloud, and Bandcamp. Radio and aggregator skills such as TuneIn, SomaFM, and News stay available.

## Hub Limit Reached

The same plan limit applies whether a hub is created in the dashboard or from code. A hub limit reached through the API returns HTTP 403 with the code `plan_limit` instead of a locked button. Reduce hub usage or change plan, then retry.

Creating a hub from code has two more boundaries that the dashboard doesn't. The API checks the plan first: on the Free plan, a provisioning call answers HTTP 402 with the upgrade message. On a paid plan, the API token also needs the hub write scope, or the call answers HTTP 403. See [Provision Hubs](/developers/provisioning/#read-402-before-403) for the plan and scope rules.

## Runtime and Live Limits

Runtime and Topology issues can look like plan problems when the wrong hub, skill set, or client is being checked.

Select Standard or [Autoscaling](/concepts/hubs/#standard-and-autoscaling-capacity)
capacity on the hub, within the limits shown in Billing. Changing runtime
settings doesn't enable autoscaling.

1. **Check Billing first** when the product shows locked, disabled, unavailable, upgrade required, or limit reached.
2. **Check service status** when several pages or teammates see the same broad problem.
3. **Check the owner page next** when Billing says the plan allows the action and status is clear.
4. **Check Topology last** when Dashboard, Clients, and Access rules look correct but live state is missing or stale.

## Safety Limits

Some actions are intentionally blocked until account or data safety checks pass:

- sensitive downloads can require account security checks;
- setup links and connection files must stay private and should be rotated if exposed;
- public support shouldn't include tokens, passwords, API keys, client secrets, customer data, setup links, or connection files;
- broad access rules should be split before adding more access.

  If a secret, setup link, or connection file was shared publicly, rotate it before continuing setup or support.

## When a Limit Looks Wrong

If Billing or the owner page shows a limit that doesn't match what you expect, include this in your support request:

- page or feature;
- plan name;
- current usage and limit;
- visible status or message;
- expected result;
- actual result;
- what changed recently.

Prepare a support request

## Limits Are Clear When

You're done checking limits when:

- Billing confirms whether the plan allows the action;
- current usage is below or at the shown limit;
- the owner page explains the next step;
- any remaining issue has a support request with plan, usage, and visible status.