@josh @emmanuel @nick.carroll Increasing the API timeout time is an extremely high bang for your buck low-hanging fruit. Having a 60-second timeout on API calls in 2025 is the equivalent of that 80 year old limestone mine that still processes all government retirements. Test-time compute is the next frontier of scaling. This is the new norm ever since o1 and Deepseek. Even Bubble AI/Assist takes several minutes to provide a response.
AI apps are the #1 use case for people who are getting into building, imagine someone on a forum asking for “which nocode tool to use” and someone responding, “Bubble doesn’t let you use reasoning models.” This is a massive impediment to growth.
On a purely strategic basis, you don’t want me to take 2 weeks to set up a FaaS and do a hacky workaround to get past this issue. The #1 rule of platform growth is to keep users from leaving your platform. YouTube and other sites have warnings that pop up saying, “Are you sure you want to leave?” X/Twitter deboosts links. Apple is well, you know, Apple. The more you incentivize users to use other services to do basic things, the more you encourage them to move off your platform for good. It’s a slippery slope. It starts out as a Cloudflare Worker, then Xano, and by the time you know it, the person has moved off Bubble for their new builds.
Please, for your own sake if not mine, flip a few switches and change the API timeout to 5 minutes. Ideally I’d want 10 minutes for o1 Pro but that might cause complexity with Workflows which time out at 5 minutes. I cannot imagine this causing problems, I doubt there is heavy orchestration around the API timeout response setting. If you’re worried about causing server strain then leave the default to 60 seconds and expose it in the Settings menu.
This is a massive win on multiple levels, it enables Bubble apps to do more impressive things, which increases the chances of a Bubble app becoming successful, which increases the chances of other people finding out about Bubble. It’s literally just finding and flipping a few switches. Please do not say the “high surface area” thing. This is essentially a Bubble Boost. Just do it and announce that Bubble can now use reasoning models in your monthly newsletter. Small amount of effort with very high upside.
Adjust workflow timeout | Bubble
Edit: Apparently you guys have done this before, so it’s possible.