> ## Documentation Index
> Fetch the complete documentation index at: https://docs.goeva.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Understand email health

> Learn how Eva checks incoming and outgoing email separately, when it alerts you, and where to resolve email problems.

An email connection has two sides: receiving and sending. Eva checks them separately so it can tell
you what stopped without hiding what still works.

## Incoming and outgoing are not the same

* Incoming: Eva can sign in to the mailbox, read the inbox, and bring in new messages.
* Outgoing: Eva can send email from that address through the provider.

One side can fail while the other continues. For example, a server may still allow reading but
reject the password when sending. The card summarizes the problem as **Needs attention** and shows a
reason such as **The password no longer works for sending**.

<Frame caption="The card explains the cause in your words and when it last worked.">
  <img src="https://mintcdn.com/evaai-85079546/UUpYIbZvk2UaACxQ/images/en/channels/email/email-needs-attention-v202608.webp?fit=max&auto=format&n=UUpYIbZvk2UaACxQ&q=85&s=979547c434979de0fe2739738608eaf9" alt="Card with Needs attention, the cause and when it last worked." width="1020" height="460" data-path="images/en/channels/email/email-needs-attention-v202608.webp" />
</Frame>

## What Eva checks

Eva observes the connection while syncing or sending. It does not send test messages on its own.

It checks whether:

* It can authenticate with Google, Microsoft, or the IMAP server
* New email continues to arrive
* The first import is progressing
* The provider revoked permission or rejected the password
* The outgoing server accepted a real send
* A temporary failure recovers on retry

<Note>
  The first import covers the last 5 days. A message older than that not appearing does not mean
  the connection is unhealthy.
</Note>

## When we email you

Eva sends an email alert when the problem is definitive and **Reconnect** is the action that can
fix it. Examples include a password that stopped working or Google or Microsoft access being
removed.

Temporary failures do not generate an email every time. Eva retries automatically and shows them
in the app when they need visibility. You receive alerts that need your action, not noise for every
provider delay.

<Tip>
  If several email accounts have the same problem, Eva may group them in one notice. Review every
  card before considering the issue closed.
</Tip>

## Open Channel health

Go to **Settings → Channel health**. Open email problems appear there alongside WhatsApp,
Instagram, Messenger, and your other channels.

Each card shows:

* The channel and affected account
* The impact of the problem
* When it started
* The action that applies

<Frame caption="Channel health shows the Email incident with its Reconnect action.">
  <img src="https://mintcdn.com/evaai-85079546/UUpYIbZvk2UaACxQ/images/en/channels/email/email-health-center-v202608.webp?fit=max&auto=format&n=UUpYIbZvk2UaACxQ&q=85&s=1ad80da4574eca6f63b1d594204df301" alt="Channel health page with an Email incident and the Reconnect button." width="2464" height="1660" data-path="images/en/channels/email/email-health-center-v202608.webp" />
</Frame>

When everything is healthy, the screen says **Everything is working**. If you followed an alert
after the problem was fixed, it says **The problem you followed here is already fixed.**

## What to do when a problem appears

<Steps>
  <Step title="Read the reason">
    Open the card. The text distinguishes a rejected password, removed permission, stopped import,
    or temporary failure.
  </Step>

  <Step title="Use the single action">
    Select **Reconnect** when Eva needs new access, or **Retry** when the connection and password
    are still valid.
  </Step>

  <Step title="Confirm recovery">
    The issue leaves **Channel health** after a successful incoming connection. The member's card
    returns to **Connected** when incoming and outgoing email are healthy.
  </Step>
</Steps>

<Card title="Troubleshoot email" href="/en/channels/troubleshoot-email">
  Reconnect after changing a password or moving to another provider.
</Card>
