Is anyone else having trouble with your webapp? It looks like the host may be down. I’m getting blank screen with just an ‘error’ message. Is anyone else’s webapp not working right now?
Hey @tiffany sorry about that. It looks like we were having a little bit of downtime earlier with our cloud platform Heroku. This should be fixed now and we’re looking into ways to prevent this in the future. Sorry again!
1 Like
Thanks! I wasn’t sure if it was something in my end or what.
Im still having error messages with anything i try to do in the web builder, shows error message everey time i try to change anything.
*Maybe a Pingable Adalo IP ? 
From south pacific I get this right now :
ping 1.1.1.1
PING 1.1.1.1 (1.1.1.1): 56 data bytes
64 bytes from 1.1.1.1: icmp_seq=0 ttl=58 time=81,622 ms
I’m also facing errors when I’m trying to add magic text in any actions in the web editor. Is this related to the server issue?
1 Like
Hey David - can you confirm that this has been fixed? I’m getting errors, especially trying to modify buttons in forms. Is there still an issue or should I be troubleshooting on my end?
1 Like
I’m also having this issue.
Actively looking into this right now. I’ll try to keep you all updated on the status.
3 Likes
@JarvisDigital @Greg @colinscatt The issue with adding magic text to an action causing an error should be fixed now. Sorry for the issue there and thanks for letting us know so we could it fixed up for everyone.
@rjp was that the same issue you were experiencing?
2 Likes
Awesome, can confirm it works properly now!
1 Like
I guess. as I read in the forum, many of us got the magic text problem 
Sorry! We were working on something for the upcoming Component Marketplace that looks like it caused the issue with magic text in button components. Should be fixed now. Let us know if there are any other issues. Thanks for hanging in there with us while we fixed it.
1 Like
Yeah unfortunately for me too, it’s come up a few times, even though it later went away. No idea why it happened, but would still like to know so that I can address any of my client-facing apps that face this same issue