Back to rankings

Lovable: See Why a Connector Request Failed

LovableView original changelog

Lovable added an Activity tab to Connectors that lists the requests an app and its project chat send through connectors. It shows status, duration, success rate and median response time, so builders can find failures and see how fast requests run. Failed requests show their error, and a Fix with Lovable button drafts a debugging message in chat.

Key Takeaways

  • A new Activity tab in Connectors lists the requests an app and its chat send through connectors.
  • Summary metrics show requests, success rate and median time for the chosen range.
  • Filters cover connector, connection type, source, time range (up to 90 days) and outcome, plus search by path or request ID.
  • Failed requests show their error, and Fix with Lovable drafts a debugging message in chat (sending uses credits).
  • Headers and bodies are never recorded, and records are kept for 6 months.
  • The tab does not cover chat connectors, direct provider calls or webhooks, and records can lag or be missing.

A Log of Connector Requests

Lovable added an Activity tab to Connectors so builders can see the requests their app and project chat send through a connector. It is meant for finding failures and checking how quickly requests run. To open it, go to More, then Connectors in a project, and select Activity. The tab appears only for people who can manage the project's settings.

What the Table Shows

Each row shows a status icon (succeeded, failed or cancelled), the connection used, the response code such as 401, the method and path, the time and the duration. Rows load 50 at a time, newest first, with a Show more button. Summary figures at the top show Requests, Success rate and Median time for the selected range.

Filtering

Builders can filter by connector, by connection type (App + chat or App users), by source (App, meaning the app's credentials, or Chat, meaning requests Lovable sent on your behalf), by range (last hour, 24 hours, 7 days, 30 days, or a custom range up to 90 days) and by outcome. A search box matches a path or request ID. The outcome buttons and search do not change the summary figures.

Debugging a Failed Request

Selecting a row shows the full path, request ID, connection and source, and for failed requests the error. Common causes include an expired credential, a missing permission or rate limiting, though some failures show no cause. For an expired or rejected credential, reconnect the account. To get help from Lovable, select Fix with Lovable in the project chat. Lovable drafts a message describing the request and error in the chat input; the builder reviews and sends it, and sending uses credits. Builders can also ask Lovable in chat to review recent activity.

What Is Not Covered

The tab does not cover chat connectors (MCP servers), requests an app sends directly to a provider without a connector, or incoming webhooks. Project logs cover those.

Data Handling

Records show what the request was and how it ended. Headers and bodies are never recorded. Records are kept for 6 months. A record can take a few minutes to appear and some may be missing, so an empty list does not prove that no request was sent.