Thank you for the bug report! Our team is investigating this behavior now and will update you all as soon as possible.
4 Likes
Any updates on this?
1 Like
Was working with support on it.
I isolated the issue to a Re-Usable element that was trying to create a piece of Data. When it was referring to a State within the same re-usable element it was creating the piece of data correctly on page but not saving it correctly to the Database - breaking subsequent workflows and creating orphaned data
I implemented a fix to no longer refer to the State the same way, and instead moved the piece of data from the state to a Group on page.
Example, in the image below the Reference element was Re-usable Elements’ Current Order (a state), but is now moved into a Group in the element
Note - the above uses the deprecated ‘Create if doesn’t exist feature’ which we thought was the issue at first, but the same result happened with a Create Data Action and a Condition on it referring to the State
2 Likes
Should also add that the issue has been escalated to the Engineering team, so hopefully they will have a fix. But if you need to fix it ASAP in your app try looking for situations like I described above. I might have another spot with this issue but without data creation, just referring to a re-usable’s state. Looking into it now
All of this is within the Custom workflows in Re-Usable elements though too, so maybe the issue is with those specific type of workflows, as Schedule API Workflows form a Re-Usable Custom Workflow seem to be broken for me
chiming in to say our site is experiencing all the same bugs with the same inputs as @gf_wolfer:
- page uses a reusable element to create data.
- am also managing various pieces of state on that reusable element
- am on immediate release (that’s a default that i didn’t even notice until now)
submitted a bug report but haven’t heard back yet. this reusable-element-to-create-data-and-manage-state is a paradigm we use site-wide, so changing the how state is used won’t be a quick fix for us. will continue to follow along on this thread, and look forward to any further details!
1 Like
We facing this issue and it’s CRITICAL for us to solve this. Users are making payments and are not being created because of this. This is affecting our business! We already submitted a bug report but need the solution ASAP!
1 Like
Just so you know. We use a lot of reusable elements, and we have one that is responsible for all our registrations in our platform and user activation. Since it’s not working users are having a terrible first time experience. Is there any ETA here?
1 Like
It’s over 8 hours since the broken update was pushed. Can we please get some kind of status update
2 Likes
@jess
Any status updates to calm our nerves? All of my client’s production apps are broken.
1 Like
I haven’t heard any updates. I would recommend coming up with very specific and reproducible examples and sending in bug reports so the engineers can test things, since that’s what they asked me to do.
I couldn’t wait for the fix so I put in work arounds for the key parts of my app and hope they can get the bugs fixed ASAP as there still some non functioning parts I couldn’t work around (scheduled API workflows in a reusable element’s custom workflows)
1 Like
Dang… so frustrating… And still no response… Is these type of situations that makes us wonder if we can rely on no-code tools.
Have faith in the 99.9 % uptime!
Even God had to reboot the system once.
-Bubble 3:16
1 Like
Seriously, has no answers for your customers?? Your status page is everything all right, neither there we can follow what is happening, really disappointed with your support…
1 Like
I’ve started getting reports of errors today as well.
I have a stack of reusable elements with custom workflows and states 
I’m sure they’ve seen this and are working as fast as they can on a fix
@jess @eve Is there some update here? It can’t be real that you guys don’t event give a position about it
Still a lot of errors occurring here. But also noticed that some errors are being reported in the logs but thankfully things seem to be working on the page now… @bubble @jess @eve
The last error log here did not actually show a prompt to me on the page and seemed to fully work, despite being shown here in the logs
Hello, everyone,
Appreciate you sending those additional bug reports and reproducible cases along! This is high priority for our engineering team to resolve, and they are continuing to work on a fix for this. We will let you know as soon as this is live; thank you for your patience!
1 Like
has anyone had similar issues with workflows related to send email api ?? or is coincidental that this is failing too ???
didn’t Bubble say they had a DDOS attack over the weekend ??
I just submitted a very simple, reproducible demo of this bug. Bug report #16247