What to Do If Your Bubble App Hits Its Database Entry Limit
Overview
If your Bubble app displays an error message such as "This application is at its limit for number of Things in the database," it means your app has reached the maximum allowed number of database entries (referred to as "Things") for your current plan. For Free plan users, this limit is 200 entries across both the Development and Live databases combined. Below, we'll explain how to identify this issue, potential resolutions without upgrading, troubleshooting tips, and when upgrading might be necessary.
Understanding the Database Limit
Why Am I Seeing This Error?
This error occurs when the number of database entries ("Things") across your Development and Live databases meets or exceeds the limit for your current plan. On the Free plan, this limit is 200 total entries. Free apps can create entries in both the Development and Live databases, even if Live database access is restricted for Free plans. This message may also appear in associated email notifications that inform you of this limit.
Resolving the Database Limit Issue Without Upgrading
If you do not want to upgrade your plan, you can resolve this issue by reducing the total number of entries in your databases:
Count Existing Entries: - Navigate to your app's Development database and count the total number of entries. - Switch to your Live database and count the entries there as well, if applicable.
Delete Unnecessary Entries: - Identify and delete database entries that are no longer needed in both the Development and Live databases. - Ensure that the combined total of entries across both databases is less than or equal to 200.
Why the Error Persists After Deleting Entries
If the error persists, check that the number of entries in your Development database alone does not exceed the limit. The Live database does not need deployment to count against the limit, so always verify both databases.
Troubleshooting Environment-Related Issues
In some cases, the database limit error might appear in connection with your browser or editor environment rather than database content. Common solutions include:
Clear Browser Cookies and Cache: Poorly cached data can contribute to editor errors. Clear your browser's cookies and cache from the settings menu thoroughly.
Restart Your Browser: Ensure the browser is fully exited and restarted—not just the tab or window.
Try a Private or Incognito Window: Open your Bubble app's editor in a private window and check for improvement.
Disable Extensions: Some browser extensions may interfere with editor functionality. Disable them one by one to troubleshoot conflicts.
Switch Browsers: Access the editor in a different browser to rule out browser-specific issues.
When to Consider Upgrading
If your app consistently requires more than 200 database entries, you may need to upgrade to a paid plan. Upgrading removes the entry limit entirely, allowing for unrestricted data growth. Paid plans are particularly important for scaling apps or managing complex databases.
Conclusion
Managing your Bubble app’s database within the 200-entry limit is possible by carefully monitoring and deleting unnecessary entries. However, upgrading to a paid plan is the best option for apps requiring more extensive database storage. If troubleshooting environmental issues fails to address your concerns, or if you continue to experience related problems, contact Bubble support for further assistance.