My app stopped working and I changed nothing: what to check

1. Open the app in a private browser window.
2. Open the app on a different device and on a different network.
3. Press F12 to open the browser tools.
4. Click Console and read the red errors.
5. Click Network and load the page again.
6. Find the lines in red and write down the status numbers.

The status number tells you where to look.

• 401 or 403: The server did not accept the request. Examine the keys, the sign-in and the access rules.
• 404: The address does not exist. Examine the address and the last deployment.
• 429: The app sent too many requests. Examine the limits of the service.
• 500: The server has an error. Read the logs of the server.
• 502, 503 or 504: A server or a service does not respond. Examine the status of your services.
• Failed to fetch: The browser did not get a response. Examine the address and the status of the service.

An automatic process can change an app when you do nothing. Make sure that this did not occur.

1. Open your repository on GitHub and click Commits.
2. Read the date of the last commit.
3. Open the deployment page of your host and read the date of the last deployment.
4. Compare these dates with the time of the first error.

If a change occurred before the first error, return to the previous version. Read how to update packages or how to recover a Lovable app.

Open the status page of each service that your app uses. Examine the host, the database, the AI service and the payment service. If a service shows an outage, wait for the service to return. Do not change your code for a problem outside your app.

Supabase can pause a project on the Free Plan after 7 days of low activity. Supabase sends a warning email about one week before the pause. If your app has few users, examine this cause first.

1. Open the Supabase Dashboard.
2. Select your organization and the paused project.
3. Click Resume project and confirm.
4. Wait for the project to start.
5. Test your app.

The project returns to its previous state, with its data and configuration. Supabase does not pause paid projects for low activity. Read the current Supabase rules, because these limits can change.

A service can stop your app if the app reaches a limit or if a payment fails.

• The host has limits for traffic and for build time on free plans.
• The database has limits for size and for connections.
• An AI service stops when your credit balance is zero.
• A service can stop your account when your card expires.

Open the account page of each service. Find limits and failed payments. Read the warning emails in your inbox and in your spam folder.

A key lets your app use a service. A key can expire. A provider can also stop a key if the provider finds the key in public code.

1. Open the page of keys at the provider.
2. Make sure that the key is active.
3. If the key is not active, make a new key.
4. Put the new key in the secret settings of your host.
5. Deploy the app again.

Do not put a key in your code. Read how to check for exposed keys.

1. Open the account at your domain company and read the expiry date of the domain.
2. Make sure that the DNS records point to your host.
3. If the browser shows a certificate warning, open your host and read the status of the certificate.

A service can remove an old version of its API. Your app then gets errors when you make no change. Read the change log of each service. Read the emails from the provider about old versions.