Hello. I started receiving this error just minutes before I received a message that there is an issue and it is being monitored. I don’t think I did anything to cause this.
Does anyone know what might have caused this, or if there is anything I can do to try and resolve it? I really cannot wait until Monday. I will loose the entire weekend which is my main time available to work on my app. Plus, I’m preparing to release it shortly for beta testing.
Yea… have you tried mashing the “OK” button until it lets you hide it, then reverting your app to an earlier time?
I just checked my editor and it seemed fine. That fix they posted was for the real-time data issue people were seeing today… not sure if it is related…
I pressed the OK button many times, but it never releases the dialog. The editor is not receiving that error, so I suppose I could try reverting it to my last save point, but I’m nervous to do so not knowing what the cause of this error is. I don’t want to cause even more problems.
That’s one frustration I have with Bubble. There is no way to really have a “backup” of my app. If something happens to it and the editor can’t recover it, I’m ******.
UPDATE: Thank you @tylerboodman . I have found the error and it was me!
I kept pressing the OK button many more times. Finally the dialog dismissed. I was able to discover that I had a custom event that indirectly called itself causing server errors and this dialog.
I still don’t understand why it was self-referencing (it doesn’t look like it), but removing one step caused this error to go away.
Thank you so much for your (and everyone else’s) help.
The thing is, it didn’t point to itself exactly. The server error said “directly or indirectly”. So I went down the rabbit hole. I had a chain of custom events where one calls the next as its last step. Something like this:
Custom event 1:
step 1
step 2
step 3 Trigger Custom Event 2
Custom event 2:
step 1
step 2
step 3 Trigger Custom Event 3
Custom event 3:
step 1
step 2
step 3 Trigger Custom Event 4
and so on…
On custom event 5 (I think) in the chain, there was a step “Trigger Custom event 1” leftover from some earlier troubleshooting. Clearly it is not correct to have that there, but it was not easy to find it and see what was happening!
If you need to do an infinite loop (which is completely fine) or chain custom events dont use Trigger just do Schedule 0.01 seconds
Triggering Event 2 will run the event, then Event 1 will wait for it to complete then come back, so you could imagine its like an infinite tree if all of those are waiting for each other to finish then Custom Event 2’s grandson kills Custom Event 5 grandma and causes a paradox
Schedule will just fire the event and end the workflow
Interesting. The infinite loop was a mistake. I don’t need that.
If I use scheduling 0.01 seconds, how does that ensure the order of events? I was shown to trigger the next custom event. I will try it with schedule. Thanks for the tip!
