A new chat did allow the changes to apply.
Any updates on this? Seems to be blocking all conversations at the moment - some long work has now been blocked. Are those credits wasted or will I be able to access the conversation again once fixed?

There was an outage in an upstream provider for approx 1 hour that prevented creation of new conversations.
Wasnāt able to resume the conversation, but all data was kept by forking. Use that feature ![]()
Iām re-enabling BubbleScript for all projects, you can still opt out manually again but BubbleScript will soon be mandatory so if you ran into issues initially, those are likely resolved!
Quotes from users:
wow buildprint is so fast. probably 5x faster than a month ago
Buildprint is mind blowing
Also it build an end to end feature perfectly and mostly one shot
Everything that I give it, it can do
Also out of interest how often are people finding Buildprint writing āinvalidā Bubble? Like where it creates an issue checker issue?
I havenāt seen one in weeks but looking to close any remaining gaps
Cursor model?
Claude Fable 5.1
It looks like itās Claude being dumb and running a background command that never ends, but we shouldnāt allow this to block future messages so will fix
(we timeout sandboxes after 30 minutes of inactivity else it would stay running and eat up your agent runtime)
Howās everyone doing
will our streaks be affected by todayās outages
?
yes, do better
I honestly have a hard time keeping up with how quickly BuildPrint is evolving. At this point, I actually think Bubble should make an exception and create a dedicated category for BuildPrint here on the forum. ![]()
That said, Iām curious if anyone has already tested it for the following use caseā¦
I have a pretty large SaaS app that, for quite some time now, can no longer handle Bubbleās built-in optimization tool. Even after following all the tips people have shared here on the forum, I always end up hitting the same memory error. This issue has actually been pretty well documented here already.
Another relevant problem is that many errors simply donāt show up in Bubbleās error counter at all, so they can easily go unnoticed. Sometimes I only discover them after something breaks and I start investigating, only to find some dynamic expression somewhere highlighted in red.
Would BuildPrint be able to help with this kind of work?
Specifically, could it analyze a large app looking for optimization opportunities and also identify broken dynamic expressions or other errors that Bubbleās own error checker might be missing?
Iāve seen a few lately when it creates an input box with a specific type (text, integer, etc..) For some reason there was an error in the checker and I had to reselect the input type.
I would say the answer to your question is definitely yes based on personal experience from my use cases
Particularly in the last month or so the improvements have really made it like having a intermediate/senior engineer on the team for a fraction of the cost and much faster. Still needs to take personal leave from time to time but we can forgive that ![]()
ya
and youāve got nothing to lose by trying
i will say, we donāt allow certain things like hard deleting data types or option sets which is what the optimisation tool does. thatās purely a product choice rather than a limitation as I want to have guardrails to stop people screwing themselves over easily
Next time you see it, fix it in editor, ask Buildprint to resync, then tell it to submit bug report
Really been bugging me for years⦠Thereās so much old crap that I really wish you could delete permanently; useless option sets, fields, data types. At least Buildprintās helped us find elements on pages, reusable elements, backend workflows etc. that were no longer in use.
The āThinkingā that appears for a few seconds at a time when using Claude models showed this: āSince the Revoke popup shows no diff in either sync commit, whatever the user changed there isnāt visible in source ā maybe fixed via editor style overrides that BubbleScript doesnāt capture.ā
The only change I made was to select a style that was marked as āOverriddenā because Buildprint excluded a popup background color. Looks like every time BubbleScript is selecting an existing style, an ā(Overridden)ā suffix appears. So, does this mean changes to styles wonāt be applied to elements added by Buildprint?

