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

# Connector activity: see and fix failed connector requests

> See the requests your Lovable app and project chat send through a connector, with the status and duration of each, and ask Lovable to fix one that failed.

Lovable records the requests your app and your project chat send through a [connector](https://docs.lovable.dev/integrations/app-connectors.md) in your project's **Activity** tab. Use the tab to find out why a request failed, how often requests fail, and how long they take, instead of guessing from your app's behavior.

Open [**More → Connectors**](https://docs.lovable.dev/features/projects/editor.md#the-more-menu) in your project, then select **Activity**. The tab appears if you can manage the project's settings.

## Find a request

The **Activity** tab opens on the last 24 hours and lists the most recent requests first. Each row shows:

* An icon showing whether the request succeeded, failed, or was cancelled.
* **Connection**: the connection the request used.
* **Status**: the response code the request came back with, such as `401`.
* **Path**: the method and path the request used.
* **Time**: when the request ran.
* **Duration**: how long the request took.

The table loads 50 requests at a time. Select **Show more** to load the next 50.

Narrow the list down to the request you are looking for:

* **Connector** limits the list to one of the connectors your project has used.
* **Connection type** limits it to **App + chat** or **App users**. See [app connectors](https://docs.lovable.dev/integrations/app-connectors.md) and [app user connectors](https://docs.lovable.dev/integrations/app-user-connectors.md).
* **Source** limits it to **App**, the requests sent with your app's credentials, or **Chat**, the requests Lovable sent on your behalf.
* The range picker covers the last hour, 24 hours, 7 days, or 30 days. You can also set your own range, as far back as 90 days.
* **All**, **Succeeded**, **Failed**, and **Cancelled** limit the list to one outcome.
* The search field matches a path or a request ID.

Above the table, **Requests**, **Success rate**, and **Median time** summarize the range, connector, connection type, and source you selected. The outcome buttons and the search field do not change them.

Select a row to see its details. These include the full path, the request ID, the connection, and the source. A failed request also shows what went wrong.

A failed request usually names a cause you can act on, such as an expired credential, a missing permission, or too many requests in a short time. Some failed requests name no cause.

When a credential expired or the provider rejected it, reconnect the account. See [Gateway connectors](https://docs.lovable.dev/integrations/security.md#gateway-connectors).

## Fix a failed request

Open the project chat first, because Lovable writes its message there. Then select **Fix with Lovable** on the failed request.

Lovable writes a message describing the request and its error into the project chat input. You read the message and send it yourself. Nothing reaches Lovable until you send the message, and sending it is treated as standard build usage and consumes credits.

You can also ask Lovable in the project chat to read these records itself, so you can describe the problem in your own words:

```text wrap theme={null}
Our Stripe calls started failing this morning. Check the connector activity for the last few hours and tell me what changed.
```

## What Lovable records

The **Activity** tab covers the requests your app and your project chat send through a connector. It does not cover:

* [chat connectors (MCP servers)](https://docs.lovable.dev/integrations/chat-connectors.md)
* requests your app sends directly to a provider without a connector
* webhooks other services send to your app

Check your project's [logs](https://docs.lovable.dev/features/logs.md) for webhooks and for requests your app sends directly.

A record shows what the request was and how it ended, not what it carried. Lovable never records request or response headers or bodies. Lovable keeps a record for 6 months, as described in [Data retention and deletion policy](https://docs.lovable.dev/integrations/security.md#data-retention-and-deletion-policy).

A record can take a few minutes to appear, and a record can be missing. An empty list does not prove that your app sent no request. When you expect a request and do not see it, refresh the list.

When the table cannot load, your connectors keep working. Only this view is affected, so try a shorter range or come back shortly.