![](https://cdn.discordapp.com/avatars/249692671893962762/141886634a3c74652753dae559e012a2.webp)
Getting a 500 error in some of my collections, suspecting it's because of a relationship error caused by another collection that I have now deleted (but the error persists)
![](https://cdn.discordapp.com/avatars/462046107556511744/504fd808296728e8e89d82b8ea1e77a9.webp)
You might need to recreate the collection 😕
Btw, we worked on improving stuff like this and should be released on cloud in a couple weeks
![](https://cdn.discordapp.com/avatars/249692671893962762/141886634a3c74652753dae559e012a2.webp)
Really? There's no way to restore/fix this?
![](https://cdn.discordapp.com/avatars/249692671893962762/141886634a3c74652753dae559e012a2.webp)
How can I avoid that this happens in the future? These were my biggest/most important collections
![](https://cdn.discordapp.com/avatars/462046107556511744/504fd808296728e8e89d82b8ea1e77a9.webp)
Not really.
![](https://cdn.discordapp.com/avatars/462046107556511744/504fd808296728e8e89d82b8ea1e77a9.webp)
Does the stuck attribute cause any problems?
What's the 500 from?
Also, keep in mind relationships is experimental
Recommended threads
- Error uploading more than 1MB
- Access blocked by CORS policy
Getting the following error message while uploading or updating image files at Appwrite Storage. ``` Access to XMLHttpRequest at 'https://cloud.appwrite.io/v1/...
- Many to many relationships restrictions ...
Hi! I'm creating and testing a simple data model and I'm a bit confused about how one way relationship restrictions work with many to many relationship. I will ...
![](/images/bgs/pre-footer.png)