> For the complete documentation index, see [llms.txt](https://docs.fastn.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.fastn.ai/build/connections/statuses.md).

# Statuses

What Active, Inactive, Expired and Failed mean, and what to do about each.

Every connection has one status. It shows in the **Status** column on the [Connections](/build/connections.md) page, on the connector's **Connections** tab, and as a badge on the [connection's detail page](/build/connections/inside-a-connection.md), where a one-line explanation sits next to it.

| Status       | Meaning                                                                       | What to do                                                                                   |
| ------------ | ----------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------- |
| **Active**   | The connection works.                                                         | Nothing.                                                                                     |
| **Inactive** | The connection exists but is not active.                                      | **Reconnect** it, or **Disconnect** it if it is no longer needed.                            |
| **Expired**  | *Authorised, but the credential has expired. Reconnecting usually clears it.* | **Reconnect**. For a customer's connection, the customer signs in again through your widget. |
| **Failed**   | The credential is not accepted.                                               | Same as Expired: sign in again.                                                              |

Use the status chips at the top of the Connections page to list only connections in one state.

{% hint style="info" %}
A workflow that runs through an Expired or Failed connection cannot reach the app. Check connection status when a sync stops, and set an [alert](/operate/alerts.md) so you hear about a broken connection before your customer does.
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.fastn.ai/build/connections/statuses.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.