# Health and monitoring

What happens when an integration cannot deliver: how Formstep retries, when it pauses an integration, and how you turn it back on, retry failed deliveries or reconnect an account.

## Where you see a problem

- The Integrations button in the form’s top bar shows an amber dot.

- In the form’s Integrations dialog, the integration’s status line under **On this form** names the problem.

- Open the integration and a banner says what happened and what to do.

- The person who set up the integration gets an email, at most one per integration a day.

## What each status means

| What you see | What it means | What to do |
| - | - | - |
| On | Submissions are sent as they come in. | Nothing. |
| Paused | You turned it off, or Formstep paused it after repeated failures. | Fix the cause, then turn its switch back on. |
| Connection expired | The account behind it no longer lets Formstep in. | Click **Reconnect** in the banner. |
| Lost access to the destination | The connected account can no longer write to the spreadsheet, database or channel. | Share it with that account again, or reconnect with an account that has access. Then click **Reactivate**. |
| Destination not found | The spreadsheet, database or channel no longer exists. | Delete the integration and set up a new one. A Linear team or GitHub repository can be changed in place instead. |
| Delivery failed | Recent deliveries failed for another reason. | Read the error under **Recent events**, fix it, and click **Reactivate**. |

## Retries and failed deliveries

When a delivery fails, Formstep tries it again on its own for about two hours. Most short outages at the destination clear up within that time without you noticing.

If every try fails, the integration shows a banner such as “3 submissions failed to deliver”. Fix the cause, then click **Retry all** to send them again. Retry all also turns the integration back on if it was paused. Formstep keeps every submission whatever happens to an integration, so you can retry the failed ones later.

## When Formstep pauses an integration

After 5 failed deliveries in a row, Formstep pauses the integration and emails the person who set it up, or the workspace owner. It pauses at once when retrying cannot help, for example when access was revoked or the destination was deleted.

To turn it back on, fix the cause, open the integration and turn its switch back on. If it shows an error banner, click **Reactivate** instead. New submissions are sent again from then on. Use **Retry all** for the ones that failed in the meantime.

## Reconnecting an account

Formstep keeps each connected account signed in on its own. When that stops working, for example because someone revoked Formstep’s access in the other tool, the integration shows **Connection expired**. Click **Reconnect** and sign in again. Every integration that uses that account starts working again.

If the original account is not available, reconnect with another account that has access to the same destination.

## Recent events

Each integration lists its last 20 events under **Recent events**: deliveries, tests and copies of past submissions. A failed event shows the destination’s own error message, which usually says what to fix. A failed copy of past submissions has a **Retry** button.

> **Google Analytics and Axiom work differently**
>
> Analytics events are sent once and never retried. See [Analytics](https://formstep.io/docs/integrations/analytics-streaming/).

## FAQ

**Will I lose submissions if an integration goes down?**

No. Formstep saves every submission whatever the integration’s status. Send the failed ones again with **Retry all** once you fix the cause.

**What if I reconnect with a different account?**

The integration uses the new account. Make sure it can reach the same spreadsheet, database or channel, or change the integration’s setup.

## Next steps

[Integrations overview](https://formstep.io/docs/integrations/overview/) — Every tool Formstep works with

[Custom webhooks](https://formstep.io/docs/integrations/webhooks/) — Send each submission to your own URL