I come here because it may be the only place where support responds. Two weeks ago my application went offline for all my users, but 10 days before I was already warning what was happening and support did not handle the error. Now again a simple POPUP turns into a loop until it gives an error. What I ask Emanuel is an answer and solution from Bubble because I am losing credibility with My App. Please, I have been asking for help for a while.
And just one more thing that I had warned support about. All of this started after they released Mobile. They can even remove it, but I can’t stand still any longer. I’m losing customers.
@emmanuel
This is happening because you are using two seperate workflows for the same button. Its a bug since mobile has launched.
Create seperate buttons for each condition. It should work just fine.
Not an ideal solution.
If that’s the case, it’s absurd — in this flow I don’t have this kind of action. But I do in others, and what’s worse is that the app crashes for all users, only working sometimes in mobile mode. I’ve already lost clients because of this. To make things worse, support told me that the team will only look into it on Monday.
Very discouraging, on top of the lost credibility and clients.
@emmanuel please ask to remove the mobile version from my app until the problems are resolved. I have a SaaS, and I work in a niche market where I might end up losing an entire project that I’ve been working on for two years. I know you are trying to deliver a platform with more components, but we can’t go through problems like this.
@nocodeventure
Thank you for the help
1 Like
No worries, during the beta phase it’ll probably be faster to do it this way.
‘Workflows could not run because too many events triggered at the same time’
Just adding the sentence in this post so others can find it.
1 Like
This popup has been in my system for over a year in the live version. It started after the introduction of the Mobile version. There isn’t much sequence in this flow — it simply creates a user, sends a normalize call to the backend, and resets the inputs.
There was a time when I spent 26 hours on the system trying to identify an issue where a simple “show” action triggered the same event. On that day, Bubble reported it was a platform issue — but only after those 26 hours. By then, I had already rebuilt the entire app on another page, thinking the menu was the problem. Later, a friend from the community found that it worked on Mobile, but I never got a more concrete explanation.
I really hope this gets analyzed because the credibility of my app is at stake — especially in such a small niche.
I truly like Bubble, but some things on the platform are starting to worry me. I understand it’s a phase, but during this phase, we need Bubble to look at its partners with more care.
This is marked as a solution, but it’s not the solution in my case. Advanced users from the Bubble community in Brazil have looked into my issue.
I also forgot to mention that this issue is intermittent. Every time I open a ticket, it seems to start working again after some time — like it did yesterday. However, it keeps happening, and the last time, the entire application stopped working.
