# See whether your connections are working

Source: https://frosvo.com/docs/connection-health
Updated: 2026-11-12

See at a glance which channels, mailboxes, webhooks, account connector and email servers are working, failing or paused, based only on what Frosvo has actually seen.

When something stops working, customers usually notice before you do. The connection health card lists every outside connection of your workspace and says whether it worked the last time Frosvo tried, so you can see problems early and know which ones need you.

## Before you start

Open **Settings → Operations → Problems**. The card sits above the list of problems. It appears once you have at least one connection: a channel, an incoming mailbox, a webhook, the account connector or a website email server.

## What the states mean

- **Working:** the last observation succeeded and is recent.
- **Not confirmed lately:** it worked once, but nothing has confirmed it for two weeks. Run a check.
- **Failing:** the last attempt failed and nothing has worked since.
- **Paused:** Frosvo stopped using it, for example after repeated webhook failures or when a channel provider rejected the credentials. Fix the cause, then turn it back on.
- **Not checked yet:** nothing has been observed, so Frosvo cannot say it works.

Each line also shows when it last worked and when it last failed, and the message the other side gave when there is one. Items that need attention are listed first.

## Steps

1. Open the card and read the top lines first: paused and failing connections come before the rest.
2. For a failing channel, open **Channels**, choose **Test connection** and read the message.
3. For a paused channel, incoming mailbox or webhook, fix the cause first (for example the mailbox password in **Channels**, or the receiving address in **API keys and webhooks**), then press **Turn back on** under its line. Owners and teammates with the Channels permission see this button.
4. After turning it back on, the line reads **Not checked yet**: Frosvo will try again, but it never claims the connection works until a real success is recorded. Trigger a real use or a test.
5. Use the [problems list](/docs/problems-and-alerts) below the card to see the errors behind each failure.

## Common problems

- **Everything says Not checked yet.** Nothing has run since you set it up. Send a test, or wait for normal use.
- **A connection says Failing but works for me.** The page shows what Frosvo last saw. Run its check so a new success replaces the old failure.
- **A connection stays Paused.** It stays paused until you press **Turn back on**. Frosvo does not turn it back on by itself, and it is written to the audit log when you do.
- **It pauses again straight away.** The cause is not fixed yet. Read the message under the line, for example a wrong mailbox password.

## What your visitors see

If your account connector or your integration gateway is failing or paused, the chat widget tells visitors that order and account lookups are temporarily unavailable and that they can still message you and a person will follow up. The notice appears only on websites where order and service tracking is switched on, disappears by itself once a check succeeds, and never shows technical details. It is refreshed about once a minute.

## Related

See [problems and alerts](/docs/problems-and-alerts), [channels](/docs/channels), [API keys and webhooks](/docs/api-keys-and-webhooks), the [account connector](/docs/slack-and-account-connector), [status pages](/docs/status-pages) and [linking chats to incidents](/docs/link-chats-to-incidents).

## Common questions

### Why does a new connection say "Not checked yet" instead of "Working"?

Because nothing has been observed. Frosvo never assumes a connection works. It shows Working only after something succeeded, such as a webhook delivery, a channel check or a mailbox poll.

### When does a failing connection go back to working?

Only when there is a success that is newer than the failure. A connection that is paused (switched off after repeated failures, or rejected by the provider) also needs a person to fix the cause and turn it back on.

### Does this page contact my systems?

No. It only reads what Frosvo already recorded. To get a fresh result, run the check on that connection, for example Test connection on a channel.

### What do visitors see when a connection is down?

Only when the account connector or integration gateway is failing or paused, and order tracking is on, the chat shows a short notice that lookups are temporarily unavailable and that they can still message you. Nothing technical is shown.

### Does a failing connection prove what is wrong?

No. It shows that the last attempt failed and shows the message the other side gave. Finding the cause is up to you.
