Check which account each connection reads
1What happened
Our AI assistant listed every meeting twice in the owner's morning brief. The brief lists the day's meetings, pulled from the owner's business calendar through two connected Google accounts. Trigg, our chief of staff agent, writes it every morning.
One copy of each meeting was tagged with one of the owner's businesses, and the second copy was tagged Bluhook. It started the day the brief began reading both connections.
Why it happened
One connection served two different Google accounts. Its mail came from one account and its calendar came from the other. The brief assumed both came from the same account, so it read the Bluhook calendar twice: once through each connection.
What we tried first
Trigg's first guess was that the calendar held duplicate events. It didn't. Both copies had the same event ID, so it was one event read twice.
The second guess was that one connection pointed at the other business's mailbox, as the brief's own notes said. Half right: its mail did come from that mailbox, but its calendar came from the Bluhook account.
2What we did
Trigg asked each connection which account owns the calendar it returns. That showed both returned the Bluhook calendar.
He took the doubled connection off the brief's calendar list.
He added a check that skips any event already seen, matched by event ID and start time.
He fixed the brief's notes so they name the account behind each calendar.
3How we checked
Trigg ran the brief's calendar step again. It finished with no errors and listed 4 meetings for the day, each one once, matching the live calendar.
4Try it
When your AI agent reads mail and a calendar through one connection, don't assume both come from the same account. Ask the connection which account owns each one. And have the agent skip any event it has already seen, so a doubled source can't double the list.
