Skip to main content
Project monitoring checks your project on a schedule and alerts you when Lovable finds important issues. Lovable looks at your project code, the errors your visitors hit, and the failed requests your app sends through connectors such as Stripe or Gmail. You review the findings in Lovable and can ask Lovable to fix them. Monitoring is most useful for published apps with real visitors, projects with several collaborators, and any project you want to keep healthy between editing sessions. Monitoring helps you catch problems before your users do.
Project monitoring is in beta. It is available on Pro, Business, and Enterprise workspaces.This page is about project monitoring, where Lovable checks one app you built. Looking for a task Lovable repeats on a schedule across your workspace, such as a weekly digest in a chat? See Automations. The two are different features.

What project monitoring checks

Project monitoring checks three things:
  • Project code: Lovable reviews the code changed since the last check for broken features, broken app logic, and broken pages or controls.
  • Visitor errors: Lovable checks recent errors that visitors to your app encountered, on the server and in their browsers, and looks for underlying causes in the code. Browser errors are collected only when Visitor analytics is enabled in Project settings → General → Publishing.
  • Failed connector requests: Lovable checks the requests your app sends through a connector, such as Stripe or Gmail, and reports requests that keep failing. The same requests are listed in Connector activity.
Lovable checks visitor errors and connector requests only for published apps. Examples of findings include:
  • Sign-in errors
  • Failing payments
  • Inputs that are not saved correctly
  • Buttons and other controls that do not work
  • Failing scheduled jobs
  • Broken integrations

Set up project monitoring

You set up project monitoring separately for each project. Anyone with edit access to the project can enable or disable it. Each completed check consumes credits, as described in Cost and credits. To enable project monitoring:
  1. Open your project, then open its settings.
  2. In Project settings → General → Project monitoring, enable Project monitoring.
By default, checks run daily at 6:00, and only if the project was edited since the last check. The time uses the timezone of the person who enables monitoring. The first check runs at the next scheduled time, not immediately, even if nobody has edited the project. When project monitoring is disabled, scheduled checks stop running for that project. Scheduled checks also stop running if your workspace moves to a plan that does not include project monitoring, and resume when you upgrade again.

Change the schedule

To change when checks run:
  1. In the Project monitoring section of project settings, select Configure.
  2. Select the schedule, for example Daily at 6:00. Choose daily or weekly checks, the day for weekly checks, and the hour. The dialog shows which timezone the times use, and checks run around the selected time.
  3. Next to Runs, select the run condition and choose one:
    • Every time: a check runs at every scheduled time.
    • If edited since last check: a check runs only when the project has enough edits. Set the number under Minimum edits made, then select Done. Each change saved to your project code counts as an edit. Messages to Lovable that fail or end without changing code do not count.
  4. Select Save. The Project monitoring section shows the new schedule.
Choose a daily schedule for published apps that get visits every day, and a weekly schedule for projects that change less often. If edited since last check avoids spending credits on checks when nothing has changed.

Review and fix findings

Lovable tells you about findings in two places:
  • In the editor: People with edit access see a summary of findings above the project chat.
  • By email: The project owner receives emails for important or time-sensitive findings. Each email highlights the most important new finding and links directly to it in the editor.
Select View issues in the summary to expand the full list. You have three options:
  • Try to fix: Lovable sends a message about every open finding you have not ignored to the project chat and works on them. The message is treated as standard build usage and consumes credits. You can review the changes in the project chat after Lovable finishes.
  • Skip: Closes the list without making changes. Skipped findings stay open and reappear the next time you open the project.
  • Ignore: Removes a single finding from the list, for example when it is not relevant, already resolved, or not worth fixing. To reopen a finding you ignored, select the undo button next to it before you close the list.
Lovable updates the status of a finding when you fix, ignore, or discuss it with Lovable. If you change your app another way first, the finding can be outdated. A finding from visitor errors or connector requests also leaves the list when Lovable has not seen the error again for four days. To investigate a finding before you fix it, ask Lovable about it in the project chat and name the issue. For example:

Connector findings

A connector finding can come from any kind of failed request, including a mistake in how your app calls the service. When the service rejects a connection, the finding depends on the connection type:
  • App + chat connections: The service rejected the account connected to the project through an app + chat connector. Lovable asks you in the finding to reconnect the account.
  • App user connections: The service rejected the accounts your app users connected through an app user connector. Lovable reports the rejection only when several users are affected and no request through that connector has succeeded since the first failure. The finding names the place in your app where you should ask them to reconnect.
When Lovable cannot match the connection key your app sends to a connection, Lovable asks you in the finding to reconnect the connector or copy its connection key again.

Review monitoring history

After the first check has run, the Project monitoring section in your project settings shows when the project was last checked. Select View history next to the last-checked date to see all previous checks, one row per check: Select Load more to see older checks.

Cost and credits

Each completed check is treated as standard build usage and consumes credits. The cost depends on how much code and visitor activity Lovable checks, and the monitoring history shows the cost of each check. Like other build usage, a check draws on your daily build credits before your general credits. Lovable does not run a scheduled check when the project has fewer edits than the minimum you set, or when the workspace is out of credits. A check that does not run does not consume credits.

Limitations

  • Project monitoring does not replace testing. Lovable can miss issues, especially when one check finds many issues.
  • Lovable can incorrectly flag working behavior as broken. Ignore a wrong finding so it does not appear again.

Troubleshooting

This is usually intended. Lovable does not run a scheduled check when:
  • The project has fewer edits than the Minimum edits made you set. The first check runs anyway.
  • The workspace is out of credits.
  • The workspace plan does not include project monitoring.
  • Project monitoring is disabled for the project.
A check that does not run does not consume credits and does not appear in the monitoring history. Lovable tries again at the next scheduled time. See Change the schedule to choose Every time instead.
Lovable checks visitor errors and connector requests only for published apps. If your app is not published, checks cover your project code only. Browser errors also need Visitor analytics enabled in Project settings → General → Publishing. See What project monitoring checks.
This is usually intended. Lovable emails only the project owner, and only about the most important findings. Lovable sends at most one email for a project every 3 hours, and none if you unsubscribed from Lovable emails. Open findings still appear in the summary above the project chat. See Review and fix findings.
The check did not complete and did not consume credits. If checks keep failing, contact Lovable support.
Some findings come from recent visitor error logs. The issue may have been temporary or already addressed by another fix you made. Lovable checks whether an issue is still valid before it tries to fix the issue.

FAQ

No. Project monitoring finds and explains issues. You decide whether to ask Lovable to fix a finding.
The project owner receives email alerts for important findings. Each email highlights the most important new finding. Open findings appear in the editor, where people with edit access can review and act on them.
Scheduled checks stop running for that project. Your monitoring history stays available under View history in project settings.