[SOLVED] 500 internal error

https://discord.com/channels/564160730845151244/1102936099745177700/1158507952492269668

my project id is 65111bcfe7e632a5418f

Solved now?

@ianmont

at the moment it seems that everything is fine, I was able to delete the development of a function and it didn't give me an error, thank you

we had degraded performance but it should be better now

Great!!

[SOLVED] 500 internal error

I understand, and why does it only affect some accounts? would it be possible to move my account to a more stable server, I usually use the cloud often and I always get errors of the bad server 😦

Appwrite cloud has multiple databases. The projects are being distributed across databases (a database is shared among many projects) so if a specific database fails, only the projects using such specific database will start failing

I think it's not possible to move the account for now. But you could try creating another account 🤔

oh I understand, no problem I can wait for cloud to be stable

oops the error happened again 🤔

Probably this is happening due to people doing faulty things so their "mistakes" get propagated among other projects that are in the same database. The Appwrite team is working to find what's the faulty thing that makes the database fail and to solve it

okay I understand maybe there is a user making many requests in a row, like a looped useeffect and that slows everything down, weeks ago I accidentally made a loop from a get to a document, i didn't take long like seconds to realize and I stopped it but in the overview of the cloud dashboard it increased like 3k requests and I thought that the limit of api requests in the headers would stop it but no

I don't know if it has anything to do with it, but that happened to me and it could be a cause.

Those kinds of loops should not affect at all if I'm not wrong. Maybe slowing, but not producing issues like the ones being seen. But a combination of this + faulty queries like invalid relationships could affect in some cases

oh okay, it must be complicated to fix all that, hopefully the cloud will be more stable soon

Yes, I'm pretty sure it will be identified and patched soon. It's difficult, but not impossible 😉

@ianmont can you try creating a new collection or database to test?

yes

trying...

seems to be fine