Bubble Outage
API error- Unknown error occurred get_test_api_call is not defined
1 Like
we should be up and running!
2 Likes
Is there going to be any statement on what is going on in January so far?
It has been incredibly frustrating
2 Likes
the team added postmortem explanations for what was going on last week.
Iāll see if we can update the ones from this week as well
4 Likes
@fede.bubble Thereās lot of issues since a few days reported related to API Connector. Is there any change/update that we should be aware off?
Actually, issues reported here and experienced myself:
call not showing in editor or not updated with new name
call not running or returning errors
call showing private dynamic values in editorā¦
1 Like
Iāll bet the rolled back update was a preparation for API response streaming 
3 Likes
Major issue with my API connector that my entire site runs off of.
I was wondering why my API calls were not working and I found out why. Certain fields from the API request were undefined and when I looked into the API call action in my workflow, I noticed that the fields I have checked as āPrivateā in my API call, are PUBLIC, and the ones that are not checked are the ones that are Private.
How does this even happen? @fede.bubble
Edit: This is very urgent.
1 Like
And this is why we are looking to get the āreleasesā page back @fede.bubble
4 Likes
Have you refreshed your editor?
Also, itās an editor issue - your params are still safe in the live + test run mode.
1 Like
refreshing editor fixes the call parameters problem.
I had refreshed it but this latest refresh fixed it! Thanks!
Glad to hear the params were safe, but the other big issue was that since the public fields werenāt appearing in the actionās editor, I couldnāt send any fields to the API call and every call was running into an error. Our site is a marketplace that relies on Algolia API calls so I was quite panicked to see everything was down lol.
Bubble really needs to improve itās internal QA.
Yesterday my inbox was flooded with āthings not workingā from users.
I checked them all and they are working, so then checked the forum for issues and found this.
It is extremely frustrating both for the user and the dev that every time bubble do a feature push they break something critical. Sure it gets fixed quickly (in most cases) but it kills the trust and confidence users have with the platform every single time.
Not to mention all the wasted time spent by users and devs trying to debug the problem.
This bug should have been picked up with proper QA before release.
7 Likes
At the very least an announcement of updates to core systems.
1 Like
I still donāt understand how this keeps happening over and over again. Why does Bubble not have a āstagingā branch? Itās literally just development straight into liveā¦
We used to call thatbubble.io/releases and then someone decided it wasnāt a good idea?
6 Likes
Still getting reports of issues from users where tables that rely on API calls to populate are not functioning normally. Have a call in 10 mins to try and explain why. Thatāll be fun.
1 Like
Agreed. It is seriously tiring for businesses that depend on Bubble apps minute to minute (SaaS, internal tools, etc) to be functioning as expected. Itās a bigger issue than uptime/downtime as these type of issues degrade trust in the platform.
Unfortunately I think Bubble is closest with agencies and app developers who donāt feel this pain as strongly so then Bubble also doesnāt fully feel this āpainā. Itās been 5+ years that dependability has been a priority, yet it is still common that serious in production apps still have these issues with only a āsorry we will do betterā to follow it up.
if you notice the timestamps, most of these are really only 1 issue that gets resolved/unresolved as the engineering team works on a patch.
I havenāt checked with engineering but I wouldnāt be surprised if those 5 are really 1 issue