How fresh the Attio card is
The complaint that brings people to this page is always the same shape. A colleague changes something in Attio, you refresh the Jira request, and the card carries on showing the old value. Nothing is broken. The answer is being reused, and there is no refresh control on a working card to force it.
This page says exactly how long each kind of answer is kept, what is never kept at all, and which changes skip the wait entirely.
#Nothing is synced
There is no background job, no queue and no timer. Nothing is copied out of Attio on a schedule and no copy of your CRM is kept. Every value on a card is fetched because somebody opened a request, and then held for a while so the next person to open a request for the same customer does not pay for it again.
That sharing is the point. Once one agent has opened a request from a customer, a second agent looking at another request from the same customer in the same project costs no call to Attio and no call to Jira.
#How long each answer is kept
What | Kept for | Shared by | What that delays |
|---|---|---|---|
A matched Attio record and the rows built from it | 15 minutes | Everyone looking at requests from that customer in that project | An edit made in Attio takes up to fifteen minutes to reach the card |
A confirmed no match | 15 minutes | The same | A customer newly added to Attio takes up to fifteen minutes to appear on a request already viewed |
A list of candidates | 15 minutes | The same | After duplicates are merged in Attio, the card can go on offering the candidate list for up to fifteen minutes |
An object's attribute list | 1 hour | Per project | Renaming an attribute in Attio, or adding one, takes up to an hour to show on the card and in the settings pickers |
Whether a viewer may see the card | 15 minutes | Per person, per request | Removing somebody's access takes up to fifteen minutes to hide the card from them |
A person's Jira group membership | 15 minutes | Per person | Moving somebody into a restricted group takes up to fifteen minutes to let them see the card |
Who reports a request | 15 minutes | Per request | Nothing: reassigning the reporter is noticed and read again straight away |
A record's picture | 1 hour | The viewer's own browser | A picture replaced at the same address can take up to an hour for readers who have already seen it |
The name and picture of whoever connected a project | 24 hours | The site-wide connections list | A display name change can show as the old one on that page for up to a day |
#What is never kept
Failures of any kind. A timeout, an unreachable Attio, a rejected key: used once for that view and then discarded, so one bad minute upstream never becomes fifteen minutes of an empty card.
Rate limits, from either Attio or Jira.
A permission question Jira would not answer. It is treated as no for that render only and never stored.
The value column on the Fields screen. It always runs a fresh lookup, so an administrator watching a change take effect sees the configuration they saved rather than the one it replaced.
The check that guards the settings screens themselves. Whether the caller administers the project is asked of Jira live, every time, so removing somebody's project administration takes effect at once.
Only three answers are ever kept. A matched record, a confirmed no match, and a list of candidates. Nothing degraded is stored, which is why a failing card recovers the moment Attio does rather than fifteen minutes later.
#What skips the wait
A settings change never waits out the fifteen minutes. The kept answer is tied to the exact configuration it was built from, so any of these shows on the next view of a request:
The Attio object, the attribute matched on, or what the reporter is matched on.
Either domain list, ignored or always-match.
The attributes on the card and their order.
A linked-record title, the attributes nested under a link, or the choice between showing a linked record inline and on hover.
The picture attribute, or the row the picture sits beside.
The audience, including the group restriction. Editing the group list applies straight away.
The placements, which are published the moment they are toggled.
Reassigning the reporter on a request also skips it. If the reporter changes while a recent answer is still held, the app notices the account no longer matches and reads the new reporter rather than reusing the old customer.
#There is no refresh button
A card showing rows has no control that forces a re-read, and it deliberately does not reload when you switch back to the browser window. "Try again" appears in exactly two states, which are the two where retrying is the next useful thing to do: an error, and a rate limit with nothing on screen. A rate limit with values already on screen keeps them and adds a quiet line instead: "Attio is rate limiting this app, so these values may be out of date."
The card also does not tell you how old its values are. There is no workspace name and no "updated N minutes ago" line on it. If you need to know that a value is current, open the record in Attio from the link at the bottom left.
#The site-wide connections list
A project appears on that list once an API key has been stored for it, even if setup is unfinished, and it drops off when the key is removed. The list can be up to about half a minute behind a change made a moment earlier, and the names and pictures in its Connected by column are held for a day.
#A few things worth knowing
A rename in Attio moves in two stages: the value is fifteen minutes behind, the label up to an hour, so for a while a card can show a new value under an old field name.
Editing the group list on the Permissions tab applies at once, but moving a person into one of those groups in Jira does not: their membership is remembered for fifteen minutes.
Somebody who has lost access can keep seeing the card for up to fifteen minutes, because permission answers are remembered per person. The settings screens are not: whether you administer the project is asked of Jira live, on every action.
#Related
Fifteen minutes answers most of it. An hour answers the labels.
