## TL;DR

HubSpot caps how many associations one record can have of a given type, and your create call hit the cap. List the existing associations, remove the stale ones, and only then add the new one. If you hit caps regularly, the association model needs redesigning, not more retries.

## Error

```text
{
  "status": "error",
  "message": "Association limit reached for object",
  "errorType": "ASSOCIATION_LIMIT_REACHED"
}
```

## Steps

1. GET the record's associations of that type to see the current count and what is there. Expected: you see the full list, including stale entries nobody uses.
2. Delete associations that are no longer meaningful (old campaigns, dead deals). Expected: the count drops below the cap.
3. Retry the association create. Expected: 200 with the new association recorded.
4. If caps are hit routinely, reconsider the model: use a custom object or a property instead of one more association per event. Expected: the cap stops being a weekly incident.
5. In agents, check the count before creating and prune on a schedule. Expected: steady state with headroom, not a sawtooth of failures.

## When to use

- Association creates return ASSOCIATION_LIMIT_REACHED.
- An agent that associates every touch as a new association starts failing after months of success.
- Syncs that worked on small accounts fail on large ones.

## When not to use

- CONTACT_ALREADY_EXISTS (identity, not associations).
- 429 rate limits (pacing, not caps).

## Tool compatibility

- HubSpot CRM API v4 associations endpoints.
- Private apps with association write scopes.

## Variant phrasings

### Association limit reached for object

The long form; the cap is per association type, not total.

### cannot associate: limit

Same error from batch association endpoints.

## Why it happens

Associations are the HubSpot graph, and caps keep it queryable. Agents that associate freely (every email, every campaign touch) fill the quota over months until creates start failing.

## Edge cases

- Primary associations have their own stricter limits; a record can have many associations but one primary company.
- Deleting an association is immediate; there is no recycle bin, so prune deliberately.
- Batch association endpoints fail the whole batch on one over-limit item; split and retry the remainder.

## Provenance

Resolved from the public thread: https://vectle.com/posts/pst_gAy3Ls8eD2xDCN6M2A3qCA