Bug reports
Last updated
Was this helpful?
Last updated
Was this helpful?
Bubble is a powerful and flexible platform that supports millions of apps, each with its own unique setup and requirements. While we work hard to test features thoroughly—through internal reviews, beta programs, and release checks—bugs can still occur from time to time.
That’s why user-reported bug reports are so important. They help us identify and resolve issues more quickly, contributing to a more stable experience for everyone. We truly appreciate the time and effort you and the community put into sharing detailed reports—they play a key role in keeping the platform reliable for all builders.
To ensure an efficient handling of cases and to help us solve your problem as fast as we can, we encourage you to keep in mind the points below:
Reproduce the issue: Ensure the problem is consistent and not a one-time occurrence.
Check the Bubble status page: Bubble has a that shows you if a server is having any known issues. You can also subscribe to issue alerts from the status page by clicking Subscribe to updates. Bubble's status is also visible in the AI chatbot (see ).
Check the docs: Verify if the observed behavior isn't the intended one. You can also ask a question in the .
Eliminate external factors: If using plugins or third-party integrations, to see if they are the cause. Also check your browser for ad- and or script blockers that may cause issues.
What you expected to happen Describe the intended behavior. This helps us understand what should have occurred under normal conditions.
What actually happened Be specific about the unexpected behavior you observed. If something broke, describe exactly how.
Step-by-step instructions to reproduce the issue Outline the exact steps we need to take to see the bug for ourselves. Assume the person reading has no prior knowledge of your app.
A link to the relevant part of your app If you're comfortable sharing it, include a link to the editor or run-mode version where the bug appears.
Browser and device details Let us know what browser and operating system you're using, including version numbers. This helps us rule out environment-specific issues.
Any recent changes If you’ve made changes to your app recently (e.g., new plugins, workflows, or design updates), note them. These details can sometimes point us to the source of the issue.
Console errors: If you know how to use the browser's console, inspect it for any related errors.
Bug reports are submitted through the AI chatbot in the bottom right corner of your screen. Look for this symbol:
Click the chatbot symbol to expand the chat window.
You will see a window that shows the .
Click Ask a question.
Click Report a bug 🐛.
You will be asked to provide your app's app id. You will find this in the URL of the tab where you have the editor open, for example id=my-app-id.
(Optional) You will be asked if you want to record your screen. This is not required, but can be helpful to visualize the issue you want to report.
Finally, you can provide a text description of the issue. We encourage you to follow the advise in the What makes a good bug report section. You can also attach files (such as a screenshot) to help us identify the issue.
The bug report is submitted. You can still add further details after this step if you need to.
First, let's look at how bug reports are handled:
Work hours
Bubble's bug report and support team is active 24/7
Normal response time
Bug reports will receive a response within 2 hours on average.
Response
The response is sent back via the chatbot, and the email address associated with your Bubble account.
It's difficult to set an exact timeline for when a bug is fixed, for a few reasons:
Severity and impact vary: Some bugs affect only a small number of users, while others may have broader consequences. More critical issues are prioritized accordingly.
Reproducibility: Bugs that are easy to reproduce can often be addressed faster. If a bug is inconsistent or difficult to replicate, it may take longer to diagnose.
Complexity of the underlying cause: Some bugs can be traced to a simple fix, while others may reveal deeper issues that require more time to resolve safely.
Need for testing: Even after a fix is identified, it must be thoroughly tested to ensure it doesn't introduce new problems elsewhere in the platform.
Release process: In some cases, fixes must wait for a scheduled deployment window, especially if they involve changes to core infrastructure or systems.
When it's not a bug: Some issues may turn out to be expected behavior rather than actual bugs. When that happens, we’ll do our best to explain how the feature is designed to work and offer guidance or possible workarounds to help you move forward.
