How fresh your data is
Two different things get called stale data: a person's details looking out of date, and your outreach not having happened yet. This page separates them.
Two very different things get called stale data. One is a person's details looking out of date. The other is your outreach not having happened yet. They have different causes, and the second is far more common.
Why a person's details look out of date
Public data is read live when the agent runs. There is no stored copy sitting between you and the page, so what comes back is as current as the public page itself.
That also sets the ceiling. If someone changed jobs last month and has not updated their public profile, the old role is what is published, so it is what the agent reads. Nobody can see a change that has not been published yet. The same applies to a headline, a company page, or a post.
Where a detail comes from public data across the open web rather than a page read directly, it reflects what is publicly indexed. Treat it as a strong signal, not a guarantee.
Why something has not happened yet
This is almost always the real answer, and it is pacing rather than staleness.
| What you see | What is usually happening |
|---|---|
| An approved message has not arrived | Approved messages leave during business hours at a steady pace |
| A run stopped partway through | It hit a daily limit and resumes the next day |
| Nothing has sent at all | Nothing sends until you approve it, and account actions pause if your session expires |
| A scheduled message never went | The person replied first, so it was cancelled automatically |
| An invite has no reply yet | A bare connection invite goes first, and the message waits until they accept |
Hitting one limit pauses only that action. Everything else keeps working.