Did the Fund Agent Actually Read That Source?

A connected fund inbox does not tell you whether an agent read the message you are looking for. Neither does an enabled permission or a green run. Check three separate facts: could the agent access the source, did the relevant job run, and what dates does its recorded coverage include? If one of those facts is unknown, keep the answer unknown.

Check the source before you investigate the missing item

Suppose a founder says they emailed an update last month, but the holding has no new note. It is tempting to turn the inbox signal off and back on, or to forward the email again. Neither action tells you what happened to the first copy.

In GPAgent, open Sources in the fund workspace. The Connections section shows whether the fund's mailbox and calendar are available; connection and reconnection happen in Integrations. Under What your agents check, find the activity that should have read this kind of evidence. Its visible status, latest recorded run, and coverage answer different questions. Open Details & settings only when you need to change the saved permission or inspect the recorded date windows.

What you see	What it establishes	What to do next
Mailbox is connected	The account is available to the fund's workflows	Check whether this activity is allowed and has run; do not infer that an older message was read.
A latest run is recorded	The job started or completed with the shown outcome	Compare its outcome with the coverage dates and any evidence needing attention.
“More to read in saved dates”	The recorded window still has unfinished reading	Leave the missing update unresolved; a later eligible run may continue, but there is no promised completion time.
“Saved dates checked”	The displayed, source-specific saved windows were checked	Confirm the sender, account, and date were in that scope; this is not a certificate for every inbox or all future mail.
Coverage unavailable or from an earlier source	The page cannot establish current coverage	Inspect the connection and activity history; do not translate missing telemetry into “nothing found.”

That last row matters. A successful job may have handled a recent window while older history is still being read. A change of mailbox, sender policy, or fund scope can make an earlier scan a poor answer to today's question. GPAgent labels historical or unknown coverage rather than filling the gap with an invented percentage.

Follow the problem to its owner

If Sources shows a connection problem, use its Integrations link. If it shows evidence needing review, use the link to the responsible agent or workflow and inspect the reason there. The activity row does not expose raw mail queries, credentials, or message bodies. It is an operational receipt, not a second inbox.

For the missing founder update, write down the account it reached, its approximate date, and the activity's recorded coverage before changing any settings. If it was sent to a partner's personal mailbox that the fund never connected, the fund inbox scan cannot account for it. If a message is in scope but its evidence cannot be matched to a holding, that is a different problem; the unmatched-evidence guide covers the review boundary. Do not add an unverified portfolio fact just to make the dashboard look current.

The distinction is worth testing when evaluating any agent workflow. Ask the vendor to show an actual run, the scope of the source it read, and what it does when coverage is incomplete. A demo dataset cannot prove it read your firm's inbox, but it can show whether the product admits what it does not know. GPAgent's platform describes the fund workflow; if you need to inspect these boundaries for your fund, book a demo and ask to see Sources alongside the agent's run history.

FAQ

Does “connected” mean GPAgent has scanned all our old email?

No. A connection establishes access, not historical coverage. Check the date windows for the relevant activity, and treat missing or historical coverage as an open question.

If the last run succeeded, why is an update missing?

The run outcome alone does not establish that this source, sender, and date were in scope or that every piece of evidence could be acted on. Check the activity's coverage and any review link, then verify which account received the update.

Can I press a button on Sources to force a full rescan?

Sources shows recorded work and the existing permission controls; it is not a full-history rescan button. Connection repairs live in Integrations. Do not promise an immediate retry or a date by which an older message will be read.