Entire business falling apart due to unannounced bubble failure

[nick.lockley]

So we have had our white-label eSIM marketingplace working fine for about a year now.

Today our entire platform is down and our users cannot take payments from website visitors as bubbles api connector has randomly stopped recognising _ * _ dynamic values in raw api body scripts and as of today is now c ompletely ignoring those values and instead passing the dynamic label/parameter name as a hard coded value…ignoring the dynamic value thats referenced against those labels.

So now stripe is getting sent success_url instead of the actual dynamic value/url and of course not a single one of our checkout sessions are generating as a result.

I have emailed bubble support as they have not mentioned this in their service outages page & am currently receiving about a million emails from users threatening to leave our platform.

Does anyone know any escalation routes into bubble we can use to get quicker answers on this from them? Like we have about 700 users that are all going to have wasted marketing budgets over this and probably leave our platform altogether and if that happens we need to follow recourse process.

How would anyone else fix this or workaround it while bubble notices it?

I hate to sound like one of those people…but if this isnt resolved promptly our entire business is going to suffer amounts i can’t even fathom simply because we chose to use bubble to build our platform. How is it that this wasnt announced when there are clearly forum threads covering this from a week ago??? What explanation do I give to our users? What explanation do i give to our legal team??

Ridiculous situation. Never seen anything ike this in my entire career. To further add to our frustrations the service status page literally says zero incidents reported today.

[votterskog]

It’s a little bit hard to fully understand what’s going on without images, so I could be off here.
But what sounds like possible solutions would be

• use server script to put together the raw API scripts. I did this recently. Feed the dynamic value in there and you get the output. I wrote up how I did it here on the forum.
• Send it off to any other instance, make.com or boost.space and put it together correctly over there and send off to stripe.

[votterskog]

[SOLVED] How I received, modified, and resent a large JSON in Bubble using Toolbox & Backend Workflows

Hey Bubble community! I wanted to share a solution I finally cracked after 30+ hours of trial and error — in case it helps someone else out there struggling with JSON modification and external API workflows. My challenge I needed to: Receive structured JSON content from an external API (in my case, Eventbrite), Modify it — specifically update an image inside a nested object and bump the page_version_number, and Send the modified version back to Eventbrite. What d…

Here, it might be of some help. Basically instead of feeding the dynamic values into the raw api script, you feed them into server script and send that off.

[votterskog]

Some API Connector calls not substituting raw variables with dynamic values

API Calls Failures Bug Workaround - June 18

same issue happening for me now, will chase support, its a little different, if it change the param from having a space e.g. json_data to jsondata - it works but not practical as this exists in so many places in the app through various API Connector calls

Seems resolved

[nick.lockley]

that was my bug report lol, seems they instantly publish it once you submit it (thank god)

Its resolved in the last 20 mins so im assuming it was a fault they have now fixed. If we all submit the bug report i imagine it wont occur again randomly in a weeks time again