App editor not running

my app in every place has stopped functioning and my editor is not even loading its just buffering and even on the top bar there’s nothing? is this a problem with the editor cuz i tried switching pcs and WIFI’s and tried different browsers. if yall know anything or are facing the sam issues let me know.

Yes, looks like the Adalo servers are down

it always happens around the same time every month. More than half of my company depends on the data uploaded to my application in adalo this is crazy!

These are events that happen regularly in Adalo.

Each time Adalo goes down, users receive complaints, 1-star reviews in the app store, and the reputation of the app goes down.

This is a phenomenon that you will have to accept as long as you use Adalo.

really make want to shift to some other application builder.

Hi all–apologies for this. Our engineers were doing a Redis rollback and hit a snag. This is in efforts to modernize the Adalo system and speed up our infrastructure. The fix will be in shortly. I apologize again if anyone has lost progress, and we absolutely need to do a better job of providing a warning about engineering updates that may affect usability for a period of time.

I’ll update again when the current outage is fixed.
James

I also want to add after seeing other comments here–I’m not accepting the standard that’s been shown here about rolling out updates without first giving warning to everyone.

We will do better.

2 Likes

Adalo is back up and running now.

2 Likes

Hi James! Rather than a warning, I would prefer to have support available. I was quite surprised an update happened middle of the morning CET-time with, what felt like, very little support available. I created a support ticket at 9:40AM my time, there was no mention of a system outage on the status-page and only get a reply at 6:50PM. (For comparison; on weekdays, evening time, I have gotten replies in under 15 min).

Hi Judith - the change was an infra update, so the implementation happens during the quietest hours we have (3am ET on a Saturday morning). This is an industry standard, but we absolutely had process errors in 1) communication in advance, and 2) in error-checking before the change was pushed.

I can say that we’re taking significant action internally to ensure neither of these things happens again, and part of that is increasing support availability during one of these changes.

This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.