Attio for Jira limits and caps
Almost every surprise in this app turns out to be a cap doing its job. A card that shows nothing where you expected four companies, a row that stops at eight values, a list of projects that stops growing: all of them are deliberate, and all of them are numbers rather than judgements.
This page collects them in one place so you can check a behaviour against the number rather than guess at it.
#Connecting
Limit | Value |
|---|---|
Length of an Attio workspace API key | Exactly 64 characters. Anything else is refused in the browser and nothing is sent to Attio. The message reports how many characters were pasted, because a truncated paste otherwise looks like a revoked key. |
Spaces around a pasted key | Trimmed, so a paste that picked up a leading or trailing space still works. A field holding nothing but spaces is refused outright. |
Attio permissions the key needs | Two reads: reading records and reading object configuration. The read-write versions satisfy it as well. |
Keys per Jira project | One. There is no site-wide key, and the project settings page is the only place in the app that accepts one. |
How long the connection test waits | 8 seconds, shorter than the card's own budget because somebody is watching a spinner. |
#Talking to Attio
Limit | Value |
|---|---|
How long a card waits for Attio | 12 seconds. Past that the card says Attio did not answer within twelve seconds. |
Retries after Attio asks the app to slow down | One, after the delay Attio itself asks for, capped at 10 seconds. A second refusal ends that render. |
Retries after Jira rate limits the app | None. The card says so and offers Try again, and the refusal is not kept, so the next view tries afresh. |
Records a lookup asks Attio for | Four, which is one more than the card will ever list. |
Candidates the card lists | Up to three, each with its title and the date it was added to Attio. |
Calls to resolve linked records | One per distinct linked object, whatever the number of links. A record pointing at five companies and two deals costs two calls, not seven. |
Linked records resolved in one call | Up to 500. |
"4 or more" is a floor, not a count. Attio's answers carry no total and there is no count to ask for, so the app asks for one record more than it will show and reports the ceiling being hit as "4 or more records match this reporter." It never invents a number.
#Matching
Limit | Value |
|---|---|
Domains ignored by default | 165 free-mail and consumer-ISP domains, including gmail.com, outlook.com, yahoo.com and icloud.com. The badge reads "165 ignored by default" and the buttons name the same number. |
Shorter forms of a domain tried | Up to the last four parts of the reporter's host, longest first. Attio decides which of them is a registrable domain. |
Domains that can never be matched | Two families, whatever the lists say: Microsoft 365 tenant domains and Apple Hide My Email relay addresses. Only the exact domain on the always-match list overrides them. |
Records a domain may match, company matching | One and the card shows it. Up to three and the agent is asked which. Four or more and the card shows nothing at all. |
Records an address may match, person matching | Four or more still produces a list of three candidates. The four-or-more cut-off is company matching only. |
The on-screen rule for company matching is worth quoting whole, because it is the bit people argue with: "One record and the card shows it. Up to 3 and the agent is asked which one. 4 or more and the card shows nothing at all, because a domain that resolves to that many records is almost always free mail, a shared host or an email-service sending domain, and every candidate on the list would probably be the wrong customer."
The ignored list is a courtesy, not the safety rule. No list of free-mail domains can ever be complete, and an ordinary business domain can fan out to many records too. The real protection is refusing a domain that resolves to four or more records.
#What one row will show
Limit | Value |
|---|---|
Values before a row offers the rest | Eight, then a control reading "Show all" with the count and the attribute's name. The rest are brought back into the page when it is pressed. |
When several values become lozenges | When every value in the row is 16 characters or shorter. Anything longer is drawn as full-width lines that wrap. |
How far a single long value is folded | Four visible lines, with "Show more" under it. The threshold follows the card's measured width and never drops below 80 characters. |
Depth of linked records | One level. An attribute of a linked record that points at a third record is not offered and is not shown. |
Attribute types the card understands | Seventeen. A type Attio adds later renders as a row with the label and nothing under it, rather than raw data on a customer's request. |
Folding is visual only. No value on the card loses characters. Find-in-page, copying and screen readers reach the whole text whether a row is folded or not, and long unbreakable strings are broken across lines rather than cut.
#Layout
Measurement | Value |
|---|---|
Label above the value | Below about 380 pixels of card width. |
Label beside the value | From about 380 pixels, in a label column capped at 120 pixels so every extra pixel goes to the value. |
Two columns | From about 700 pixels, flowing down the first column and continuing down the second. |
A linked record revealed on hover | A panel about 288 pixels wide, narrowed when there is less room, opening on whichever side has more space. |
Hover timings | Opens after 0.4 seconds of resting on the reference line, closes 0.15 seconds after the pointer leaves, so the gap to the panel can be crossed. |
The card measures its own box rather than the window, so the same card changes shape as a reader drags the issue sidebar wider. Nothing else changes between the bands: the type size, the number of values shown and how much of a value is printed are identical at every width.
#The settings screens
Limit | Value |
|---|---|
Attributes the value column will answer for | 500 per list, and 50 linked objects per request. Past those, a row has no value shown and nothing fails. |
Wait after you stop typing a test address | 600 milliseconds, so a burst of edits costs one lookup rather than one each. |
The pause after a key is accepted in setup | About 1.6 seconds, with a thin bar counting it out, so the workspace name can be read before the next step arrives. |
#The site-wide connections list
Limit | Value |
|---|---|
Connected projects listed | Up to 2,000. |
People named in the Connected by column | Up to 400 on one page load, resolved fifty at a time. Anyone past that, or anyone Jira will not name, shows as "Unknown user". |
How current the list is | It can be up to about half a minute behind a change made a moment earlier. |
#A few things worth knowing
The ignored list is checked against shorter forms of a domain, so a reporter at mail.gmail.com is refused. The always-match list is not: it matches the exact domain as typed, so adding acme.com does not also allow mail.acme.com.
Four or more matches means two different things depending on the mode. Matching a company it shows nothing at all. Matching a person it still lists three candidates with a note that four or more matched.
The 2,000-project cap is on the inventory list only. Past it the card keeps working normally in every project on the site, including the ones the list has stopped naming.
#Related
Every number here is enforced, not advisory.
