A busy mailbox is no longer reported as disconnected
When Google briefly limits how fast a mailbox can be read, your AI employee no longer says Gmail is not connected: it is told the mailbox is only busy, and the read is tried again. A mail watch that cannot listen yet now says whose mailbox it is and who can turn it on.
What you get
- When Google briefly limits how fast a mailbox can be read, your AI employee no longer says Gmail is not connected and no longer asks anyone to sign in again: it is told the mailbox is only busy for a moment, and the read is tried again. A message or an attachment that can't be found is reported as not found, not as a connection problem.
- Your AI employee reads each mailbox more gently, and one stuck read no longer holds up the others.
- A mail search no longer leaves messages out without saying so: if part of it cannot be read, it reports a temporary problem and can be run again. Mail listening no longer skips a message it could not read for a moment; it reads it on the next try.
- When a mail watch cannot listen yet, you are told once, in plain words: your AI employee can read the mail when you ask, but hearing new mail as it arrives needs full access to mail. If the watch is on another person's AI employee, the notice says whose mailbox it is and that only that person can allow it, in their own chat with that AI employee.
- A mail watch starts by itself as soon as the mailbox owner allows full access to mail, and you are told when it listens again.
- When Gmail, Google Calendar or Google Docs is not connected or is missing a permission, your AI employee is told that only the person whose AI employee it is can connect Google or allow it, in their own chat with that AI employee.